Triple
T35255086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shene |
E1018208
|
entity |
| Predicate | earlierDesignationOf |
P12531
|
FINISHED |
| Object | Sheen |
—
|
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: Sheen | Statement: [Shene, earlierDesignationOf, Sheen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierDesignationOf Context triple: [Shene, earlierDesignationOf, Sheen]
-
A.
formerDesignation
chosen
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
B.
earlierDesignationYear
Indicates that one entity’s designation year occurred earlier in time than the other entity’s designation year.
-
C.
previousDesignationEstablished
Indicates that an earlier official designation or title for an entity was formally created or put into effect.
-
D.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
E.
historicalDesignation
Indicates that an entity has been formally assigned a particular status, title, or classification based on its historical significance.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:02 p.m.