Triple
T1889631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salle des Pas Perdus |
E41839
|
entity |
| Predicate | buildingTypeContext |
P1844
|
FINISHED |
| Object | international organization headquarters |
—
|
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: international organization headquarters | Statement: [Salle des Pas Perdus, buildingTypeContext, international organization headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingTypeContext Context triple: [Salle des Pas Perdus, buildingTypeContext, international organization headquarters]
-
A.
buildingType
chosen
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
C.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
-
D.
constructionType
Indicates the specific method or style by which something is built or constructed.
-
E.
buildingComplex
Indicates a relationship where multiple buildings are grouped and function together as a single integrated complex.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb142e41881908fc7335673a9dec3 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.