Triple
T18394217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Tapissier de Notre-Dame |
E449820
|
entity |
| Predicate | associatedWithBuildingFunction |
P16394
|
FINISHED |
| Object | cathedral |
—
|
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: cathedral | Statement: [Le Tapissier de Notre-Dame, associatedWithBuildingFunction, cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBuildingFunction Context triple: [Le Tapissier de Notre-Dame, associatedWithBuildingFunction, cathedral]
-
A.
functionInBuilding
Indicates that a specific function, role, or use is carried out within a particular building.
-
B.
appliedToBuilding
Indicates that something (such as a process, treatment, regulation, or attribute) is directed toward, implemented on, or otherwise affects a building.
-
C.
hasBuildingFunction
chosen
Indicates that a building is used for or serves a particular function or purpose.
-
D.
architectureAssociated
Indicates that there is a relationship or connection between an entity and a particular architectural style, feature, or practice.
-
E.
belongsToBuildingComplex
Indicates that one building or structure is part of, or included within, a larger building 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e51845d6708190bc96ec801e21b7a3 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.