Triple
T31344670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulevards of the Marshals |
E799409
|
entity |
| Predicate | isInsideOf |
P57262
|
FINISHED |
| Object | Boulevard Périphérique |
—
|
NE NERFINISHED |
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: Boulevard Périphérique | Statement: [Boulevards of the Marshals, isInsideOf, Boulevard Périphérique]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInsideOf Context triple: [Boulevards of the Marshals, isInsideOf, Boulevard Périphérique]
-
A.
existsWithin
chosen
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
B.
locatedInTheInteriorOf
Indicates that one entity is situated entirely within the inner part or inside area of another entity, rather than on its surface or boundary.
-
C.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
D.
isSeatWithin
Indicates that one seat is located inside the spatial bounds or interior area defined by another object or region.
-
E.
isOutgroundOf
Indicates that one entity lies outside the boundary, extent, or coverage area defined by another entity.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f172c148190b9d3939588a75885 |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.