Triple
T31329637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cour Carrée |
E798988
|
entity |
| Predicate | isOpenSpaceWithin |
P121439
|
FINISHED |
| Object | Louvre Palace complex |
—
|
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: Louvre Palace complex | Statement: [Cour Carrée, isOpenSpaceWithin, Louvre Palace complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOpenSpaceWithin Context triple: [Cour Carrée, isOpenSpaceWithin, Louvre Palace complex]
-
A.
isOpenSpaceOf
chosen
Indicates that one entity is an open, unobstructed area that belongs to, is part of, or is designated for use by another entity.
-
B.
isOpenSpace
Indicates that a given area or location is an unobstructed, accessible space rather than an enclosed or confined one.
-
C.
hasOpenSpaces
Indicates that an entity possesses or includes areas that are unobstructed, unoccupied, or otherwise open.
-
D.
hasOpenSpaceNearby
Indicates that an entity is located near or adjacent to an area that is open, unobstructed, or undeveloped.
-
E.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edf9bb0819086c9cf57538b4d0a |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:16 p.m.