Triple
T4657108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathédrale Saint-Pierre-et-Saint-Paul de Nantes |
E102435
|
entity |
| Predicate | hasInteriorSpace |
P6655
|
FINISHED |
| Object | choir |
—
|
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: choir | Statement: [Cathédrale Saint-Pierre-et-Saint-Paul de Nantes, hasInteriorSpace, choir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorSpace Context triple: [Cathédrale Saint-Pierre-et-Saint-Paul de Nantes, hasInteriorSpace, choir]
-
A.
hasInteriorFeature
chosen
Indicates that an entity contains or includes a specific feature within its interior space.
-
B.
hasPassengerArea
Indicates that an object or vehicle includes a designated area intended for carrying passengers.
-
C.
interiorSize
Indicates the size or dimensions of the inside space of an object or structure.
-
D.
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.
-
E.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd631a855c81909773737fd238a14d |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.