Triple
T9661638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antu |
E233602
|
entity |
| Predicate | partnerRank |
P89468
|
FINISHED |
| Object | consort of a chief god |
—
|
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: consort of a chief god | Statement: [Antu, partnerRank, consort of a chief god]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerRank Context triple: [Antu, partnerRank, consort of a chief god]
-
A.
rankingMember
Indicates that one entity is the highest-ranking or most senior member within a particular group, committee, or organization relative to the others.
-
B.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
C.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
D.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
E.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
- F. None of above. chosen
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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0a15e4819092ea0fb2cb6e1c12 |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:14 p.m.