Triple
T26853227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moors (fictional kingdom) |
E676113
|
entity |
| Predicate | laterRuledAlongside |
P21629
|
FINISHED |
| Object | Aurora |
—
|
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: Aurora | Statement: [Moors (fictional kingdom), laterRuledAlongside, Aurora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRuledAlongside Context triple: [Moors (fictional kingdom), laterRuledAlongside, Aurora]
-
A.
hasCoRuler
Indicates that an entity shares ruling authority or governance power jointly with another entity.
-
B.
alsoRuled
chosen
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
C.
ruledLaterBy
Indicates that one entity came under the rule, governance, or authority of another entity at a later point in time.
-
D.
laterFoughtAlongside
Indicates that two entities, who were previously in some other relationship or context, subsequently fought on the same side as allies in a conflict or battle.
-
E.
reignedUnder
Indicates that one entity exercised ruling authority or governance while being subordinate to, or under the higher sovereignty 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 27, 2026, 5:19 a.m.