Triple
T30942974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Cities of America |
E788310
|
entity |
| Predicate | stateOfInfrastructure |
P43100
|
FINISHED |
| Object | fragmented |
—
|
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: fragmented | Statement: [United Cities of America, stateOfInfrastructure, fragmented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfInfrastructure Context triple: [United Cities of America, stateOfInfrastructure, fragmented]
-
A.
infrastructureLevel
chosen
Indicates the degree or quality of infrastructure present or provided in relation to an entity or location.
-
B.
isPartOfInfrastructure
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
-
C.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
-
D.
parallelInfrastructure
Indicates that two or more infrastructure elements are arranged or operate in parallel to each other, typically serving similar functions simultaneously.
-
E.
structureStatus
Indicates the current condition or state of completion of a structure in relation to its intended design or function.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 29, 2026, 8:53 p.m.