Triple
T19270899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slavutych |
E481919
|
entity |
| Predicate | hasPlannedCityLayout |
P47409
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Slavutych, hasPlannedCityLayout, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedCityLayout Context triple: [Slavutych, hasPlannedCityLayout, true]
-
A.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
-
B.
isPlannedCity
Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
-
C.
hasStreetPlan
chosen
Indicates that an entity possesses or is associated with a specific layout or design plan for its streets.
-
D.
cityOfPlanning
Indicates the city where the planning or design activities for something (e.g., a project, event, or development) are carried out.
-
E.
isPlannedTown
Indicates that a town has been deliberately designed and constructed according to a pre-established plan rather than developing organically over time.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb8bea08190b5c65eebe67dccbb |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.