Triple
T30678767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girsu |
E780992
|
entity |
| Predicate | hasRulerAttested |
P18400
|
FINISHED |
| Object | Gudea of Lagash |
—
|
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: Gudea of Lagash | Statement: [Girsu, hasRulerAttested, Gudea of Lagash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulerAttested Context triple: [Girsu, hasRulerAttested, Gudea of Lagash]
-
A.
hasRulerProclaimed
Indicates that a ruler has formally announced, declared, or publicly proclaimed something.
-
B.
hasSignificantRuler
Indicates that an entity has or had a ruler whose leadership is considered historically or contextually important.
-
C.
attestedBy
chosen
Indicates that the existence, occurrence, or validity of something is supported, confirmed, or documented by a specified source or authority.
-
D.
recognizedAsRuler
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
-
E.
providedRulerFor
Indicates that one entity supplied or designated another entity to serve as the ruler or governing authority over a particular domain or group.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 8:32 p.m.