Triple
T37615297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearly Prince |
E935902
|
entity |
| Predicate | hasSeniorCounterpart |
P6587
|
FINISHED |
| Object | Pearly King |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Pearly King | Statement: [Pearly Prince, hasSeniorCounterpart, Pearly King]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeniorCounterpart Context triple: [Pearly Prince, hasSeniorCounterpart, Pearly King]
-
A.
hasAdultCounterpart
Indicates that one entity serves as the mature or adult version or counterpart of another entity.
-
B.
hasExecutiveCounterpart
Indicates that one entity serves as the executive-level counterpart or equivalent to another entity within an organizational or governance structure.
-
C.
hasSeniorCourt
Indicates that one court is hierarchically subordinate to another court that serves as its senior or higher-level authority.
-
D.
hasSeniorJudge
Indicates that one entity is assigned or linked to another entity serving in the role of a senior judge.
-
E.
hasCounterpart
chosen
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
Created at: May 3, 2026, 4:18 p.m.