Triple
T30168997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umma |
E766866
|
entity |
| Predicate | hasGovernmentBuildingType |
P171579
|
FINISHED |
| Object | palace |
—
|
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: palace | Statement: [Umma, hasGovernmentBuildingType, palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentBuildingType Context triple: [Umma, hasGovernmentBuildingType, palace]
-
A.
isGovernmentFacility
Indicates that the subject entity functions as a facility owned, operated, or officially designated for use by a government or its agencies.
-
B.
usesGovernmentBuilding
Indicates that an entity makes use of a government-owned or government-operated building for some purpose or activity.
-
C.
hasGovernmentalBodyType
Indicates the specific kind or classification of governmental body that an entity possesses or is associated with.
-
D.
hasLegislatureBuilding
Indicates that one entity serves as the official legislature building or physical premises where the legislative body of another entity meets or operates.
-
E.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 7:24 p.m.