Triple
T25758634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uxama |
E648672
|
entity |
| Predicate | hasTypeOfUrbanism |
P92984
|
FINISHED |
| Object | Romanized urban layout |
—
|
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: Romanized urban layout | Statement: [Uxama, hasTypeOfUrbanism, Romanized urban layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfUrbanism Context triple: [Uxama, hasTypeOfUrbanism, Romanized urban layout]
-
A.
hasUrbanDesign
chosen
Indicates that an entity possesses or is associated with a specific urban design plan, feature, or configuration.
-
B.
hasUrbanConcept
Indicates that an entity is associated with, characterized by, or incorporates an urban-related concept, idea, or design principle.
-
C.
hasUrbanPlanning
Indicates that an entity is involved in, responsible for, or characterized by activities or attributes related to urban planning.
-
D.
hasUrbanClassification
Indicates that an entity is assigned a specific urban status or category within a defined classification system.
-
E.
typeOfUrbanPolicy
Indicates the specific category or kind of urban policy that characterizes or governs a given urban-related entity or action.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 22, 2026, 4:43 a.m.