Triple
T33090904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | statue of Benoît de Boigne |
E846776
|
entity |
| Predicate | positionedAtop |
P13359
|
FINISHED |
| Object | Fontaine des Éléphants |
—
|
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: Fontaine des Éléphants | Statement: [statue of Benoît de Boigne, positionedAtop, Fontaine des Éléphants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionedAtop Context triple: [statue of Benoît de Boigne, positionedAtop, Fontaine des Éléphants]
-
A.
sitsAtop
chosen
Indicates that one entity is positioned directly on top of another, typically resting upon its upper surface.
-
B.
posedAtLocation
Indicates that an entity is positioned or arranged in a deliberate pose at a specific location.
-
C.
sitsAbove
Indicates that one entity is positioned directly higher than and vertically over another entity.
-
D.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
E.
appearsAtPosition
Indicates that an entity occurs or is located at a specific position within an ordered structure or sequence.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: May 1, 2026, 1:26 a.m.