Triple
T22195664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronchamp |
E548539
|
entity |
| Predicate | hasMaterialAtSite |
P1845
|
FINISHED |
| Object | reinforced concrete at Notre-Dame du Haut |
—
|
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: reinforced concrete at Notre-Dame du Haut | Statement: [Ronchamp, hasMaterialAtSite, reinforced concrete at Notre-Dame du Haut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialAtSite Context triple: [Ronchamp, hasMaterialAtSite, reinforced concrete at Notre-Dame du Haut]
-
A.
hasMaterialResource
Indicates that an entity possesses, controls, or has access to a tangible material resource.
-
B.
hasMaterialNearby
Indicates that one entity has a material located in its immediate vicinity or surrounding area.
-
C.
hasMaterialRole
Indicates that an entity participates in an activity or context by fulfilling a specific material-related role or function.
-
D.
hasMaterialAspect
Indicates that something possesses a physical or tangible component or aspect as part of its overall nature or existence.
-
E.
hasMaterialType
chosen
Indicates that something is composed of, made from, or characterized by a specific type of material.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae6f7a881908cf1772326f91467 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.