Triple
T29055403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urartian mythology |
E735371
|
entity |
| Predicate | hasConsortOfHaldi |
P201889
|
FINISHED |
| Object | Arubani |
—
|
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: Arubani | Statement: [Urartian mythology, hasConsortOfHaldi, Arubani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsortOfHaldi Context triple: [Urartian mythology, hasConsortOfHaldi, Arubani]
-
A.
hasGroom
Indicates that an entity has a groom, i.e., is associated with a male partner in a marriage or wedding relationship.
-
B.
hasChhatri
Indicates that one entity possesses or features a chhatri (a dome-shaped pavilion or canopy structure) in relation to another entity or location.
-
C.
hasEkadashi
Indicates a relationship where an entity is associated with, observes, or is characterized by the occurrence of Ekadashi (the eleventh day of the lunar fortnight).
-
D.
hasConsortCrowned
Indicates that an individual has a spouse or consort who has been formally crowned, typically in a royal or ceremonial context.
-
E.
hasCeremonyMonth
Indicates the month during which a particular ceremony takes place or is scheduled.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a002f0839fc8190a874d3b0d0826d7e |
completed | May 10, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a002eae7b6481909974b321e2789b7e |
completed | May 10, 2026, 7:07 a.m. |
| PDg | Predicate description generation | batch_6a002f071de88190b1fa4f5531a6cea7 |
completed | May 10, 2026, 7:08 a.m. |
Created at: April 28, 2026, 10:11 a.m.