Triple
T10433993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parmys |
E245989
|
entity |
| Predicate | reignAsQueenConsortDuring |
P59097
|
FINISHED |
| Object | reign of Darius I |
—
|
LITERAL FINISHED |
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: reign of Darius I | Statement: [Parmys, reignAsQueenConsortDuring, reign of Darius I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsQueenConsortDuring Context triple: [Parmys, reignAsQueenConsortDuring, reign of Darius I]
-
A.
reignAsQueenConsortFrom
Indicates the time period during which a person held the role of queen consort, starting from a specified date or event.
-
B.
reignAsQueenConsort
chosen
Indicates that a person holds the position and performs the role of queen consort during the reign of a monarch.
-
C.
reignAsQueenConsortOfEnglandEnd
Indicates the time or event at which an individual’s tenure as Queen Consort of England comes to an end.
-
D.
reignAsQueenConsortOfEnglandStart
Indicates the time at which an individual began serving as queen consort of England to a reigning English monarch.
-
E.
reignAsQueenConsortOfScotlandEnd
Indicates the time or event marking when an individual’s tenure as queen consort of Scotland comes to an end.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea65afe08190b91260c9267a0f14 |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:14 p.m.