Triple
T38241105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Gate |
E1013761
|
entity |
| Predicate | inWorldType |
P40428
|
FINISHED |
| Object | urban infrastructure |
—
|
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: urban infrastructure | Statement: [Iron Gate, inWorldType, urban infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inWorldType Context triple: [Iron Gate, inWorldType, urban infrastructure]
-
A.
worldType
chosen
Indicates the classification or category of world or environment that an entity is associated with.
-
B.
isOnWorld
Indicates that one entity is located on, or exists upon the surface or within the domain of, a particular world or planet.
-
C.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
D.
livesInWorldWith
Indicates that one entity exists or resides within the same world or universe as another entity.
-
E.
inWorldText
Indicates that a piece of text is displayed or present within the world or environment of a system, scene, or application.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.