Triple
T6104206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapelle Notre-Dame-du-Haut |
E136075
|
entity |
| Predicate | worldwideFameFor |
P52554
|
FINISHED |
| Object | sculptural form |
—
|
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: sculptural form | Statement: [Chapelle Notre-Dame-du-Haut, worldwideFameFor, sculptural form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldwideFameFor Context triple: [Chapelle Notre-Dame-du-Haut, worldwideFameFor, sculptural form]
-
A.
fameFor
chosen
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
B.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
-
C.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
D.
inscriptionFamousFor
Indicates that an inscription is widely recognized or notable specifically because of the referenced feature, event, content, or characteristic.
-
E.
formerlyKnownFor
Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3f8e5481909e85a60aaf319f66 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.