Triple
T14420298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monument du Centenaire |
E357564
|
entity |
| Predicate | locationEnvironment |
P853
|
FINISHED |
| Object | seaside garden |
—
|
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: seaside garden | Statement: [Monument du Centenaire, locationEnvironment, seaside garden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationEnvironment Context triple: [Monument du Centenaire, locationEnvironment, seaside garden]
-
A.
environmentType
chosen
Indicates the kind or category of environment associated with an entity or situation.
-
B.
positionOnEnvironment
Indicates the spatial placement or location of an entity relative to a surrounding environment or surface.
-
C.
nearbyEnvironment
Indicates that an entity is located in or affected by the immediate surrounding conditions or context of another entity.
-
D.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
E.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de910eb354819089d5d5a46919eb49 |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.