Triple
T20008844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narbonne Cathedral |
E494532
|
entity |
| Predicate | constructionEndStatus |
P98744
|
FINISHED |
| Object | unfinished |
—
|
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: unfinished | Statement: [Narbonne Cathedral, constructionEndStatus, unfinished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionEndStatus Context triple: [Narbonne Cathedral, constructionEndStatus, unfinished]
-
A.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
B.
constructionCompletedUnder
Indicates that the completion of a construction project occurred under the responsibility, authority, or supervision of a specified agent, organization, or governing body.
-
C.
typicalConstructionEnd
Indicates the usual or expected point in time or stage at which a construction process or building project is completed.
-
D.
buildingEnd
chosen
Indicates the point or time at which the construction or existence of a building comes to a conclusion.
-
E.
developmentEnded
Indicates that the process of creating, improving, or expanding something has been completed and no further development is taking place.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a7500481908b69f74e479f88c8 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.