Triple
T36389184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Roch Church square |
E896280
|
entity |
| Predicate | isLocatedInFrontOf |
P63831
|
FINISHED |
| Object | Saint-Roch Church |
—
|
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: Saint-Roch Church | Statement: [Saint-Roch Church square, isLocatedInFrontOf, Saint-Roch Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInFrontOf Context triple: [Saint-Roch Church square, isLocatedInFrontOf, Saint-Roch Church]
-
A.
installedInFrontOf
Indicates that one object has been placed or mounted so that it is positioned directly in front of another object.
-
B.
frontOf
chosen
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
C.
locatedOnFront
Indicates that one entity is positioned on the front side or face of another entity.
-
D.
isBehind
Indicates that one entity is positioned to the rear of another entity along a relevant spatial or directional axis.
-
E.
isLocatedToThe
Indicates a spatial relationship where one entity is positioned in a specific directional orientation relative to 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:10 p.m.