Triple
T10832803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royan |
E255664
|
entity |
| Predicate | urbanPlanningNotedFor |
P95969
|
FINISHED |
| Object | 1950s modernist reconstruction plan |
—
|
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: 1950s modernist reconstruction plan | Statement: [Royan, urbanPlanningNotedFor, 1950s modernist reconstruction plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanPlanningNotedFor Context triple: [Royan, urbanPlanningNotedFor, 1950s modernist reconstruction plan]
-
A.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
B.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
C.
notableCityCommunity
Indicates a relationship where a city is notably associated with, recognized by, or significantly connected to a particular community.
-
D.
notableCityIncluded
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
E.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
- F. None of above. chosen
Provenance (4 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7442439dc8190af59f9c8d0637c01 |
completed | April 9, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:19 p.m.