Triple
T30164048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inscriptions of Enmetena of Lagash |
E766746
|
entity |
| Predicate | mentionsCityState |
P149441
|
FINISHED |
| Object | Umma |
—
|
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: Umma | Statement: [inscriptions of Enmetena of Lagash, mentionsCityState, Umma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsCityState Context triple: [inscriptions of Enmetena of Lagash, mentionsCityState, Umma]
-
A.
containsCityState
Indicates that one entity includes or encompasses a specific city and state within its scope or boundaries.
-
B.
associatedCityState
Indicates a relationship where a city is linked to the state with which it is formally or contextually connected.
-
C.
mentionsCity
chosen
Indicates that one entity refers to or brings up a particular city in some form of communication or content.
-
D.
basedInCityState
Indicates that an entity’s primary location or headquarters is situated in a specific city within a specific state.
-
E.
governingCityState
Indicates that one city or state holds governing authority or administrative control over another specified region or 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f054d248190b5f5fabda89e172b |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:22 p.m.