Triple
T20336426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thousand & One |
E492622
|
entity |
| Predicate | isLocatedInDevelopmentType |
P2224
|
FINISHED |
| Object | mixed-use urban development |
—
|
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: mixed-use urban development | Statement: [Thousand & One, isLocatedInDevelopmentType, mixed-use urban development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInDevelopmentType Context triple: [Thousand & One, isLocatedInDevelopmentType, mixed-use urban development]
-
A.
hasDevelopmentType
chosen
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
B.
isDevelopmentLevelFor
Indicates that one entity represents the development or maturity level assigned to, or characteristic of, another entity.
-
C.
hasDeveloperType
Indicates that an entity is associated with a specific category or type of developer.
-
D.
hasDevelopmentStatus
Indicates the current stage or condition of progress or completion that something is in.
-
E.
developedWithin
Indicates that something was created, produced, or brought into existence inside a specified context, boundary, or time frame.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677eb4d5881908ea5ec5a1dd7eafa |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:23 a.m.