Triple
T16346775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbre aux Hérons |
E396951
|
entity |
| Predicate | plannedLocationType |
P104439
|
FINISHED |
| Object | urban park |
—
|
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 park | Statement: [Arbre aux Hérons, plannedLocationType, urban park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedLocationType Context triple: [Arbre aux Hérons, plannedLocationType, urban park]
-
A.
plannedLocation
Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
-
B.
locatedInPlannedCity
Indicates that something is situated within the boundaries of a city that was deliberately designed and planned rather than having developed organically.
-
C.
locationOfPlanning
Indicates the place or setting where the planning activity or process occurs.
-
D.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
-
E.
settingLocationType
chosen
Indicates the type or category of location in which an event, action, or situation takes place.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0ec7e08190982a0de8ba5da105 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.