Triple
T6329354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Griffith |
E141938
|
entity |
| Predicate | localGovernmentAreaType |
P70885
|
FINISHED |
| Object | city |
—
|
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: city | Statement: [City of Griffith, localGovernmentAreaType, city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localGovernmentAreaType Context triple: [City of Griffith, localGovernmentAreaType, city]
-
A.
localAuthorityArea
Indicates that one entity is a geographic or administrative area governed or managed by a specified local authority.
-
B.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
-
C.
hasLocalGovernmentAreas
Indicates that an entity is administratively divided into, or associated with, one or more local government areas.
-
D.
hasLocalGovernmentAreaStatus
Indicates that an entity holds the official designation or recognition as a local government area within a defined administrative system.
-
E.
hasLocalGovernmentAreaCode
Indicates that an entity is associated with a specific local government area identified by a particular code.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651197908190a30e504e2442d40f |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c064c080148190a7c3218867f1f572 |
completed | March 22, 2026, 9:53 p.m. |
Created at: March 22, 2026, 4:30 p.m.