Triple
T37326288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynasty 0 |
E926611
|
entity |
| Predicate | includesRulers |
P8531
|
FINISHED |
| Object | Scorpion II |
E127193
|
NE 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: Scorpion II | Statement: [Dynasty 0, includesRulers, Scorpion II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRulers Context triple: [Dynasty 0, includesRulers, Scorpion II]
-
A.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
B.
hasNumberOfRulers
Indicates the quantity of rulers associated with or governing a given entity.
-
C.
historicalRulers
chosen
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
D.
hasRulingPeople
Indicates that a group or entity serves as the governing or ruling authority over another entity.
-
E.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
- F. None of above.
Provenance (4 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40639f9a588190bb2684ba7288a5fa |
completed | June 27, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.