Triple
T2263384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cour Carrée |
E50088
|
entity |
| Predicate | positionWithin |
P5132
|
FINISHED |
| Object | eastern end of the Louvre Palace |
—
|
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: eastern end of the Louvre Palace | Statement: [Cour Carrée, positionWithin, eastern end of the Louvre Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithin Context triple: [Cour Carrée, positionWithin, eastern end of the Louvre Palace]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
C.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
D.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
-
E.
positionB
chosen
Indicates that one entity occupies or is located at a specific position 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.