Triple
T32009962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angoulême Cathedral |
E817371
|
entity |
| Predicate | primaryBuildingPhase |
P136119
|
FINISHED |
| Object | Romanesque period |
—
|
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: Romanesque period | Statement: [Angoulême Cathedral, primaryBuildingPhase, Romanesque period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBuildingPhase Context triple: [Angoulême Cathedral, primaryBuildingPhase, Romanesque period]
-
A.
originalBuildingPhase
chosen
Indicates the specific construction phase during which the building or structure was originally built.
-
B.
constructionPhase
Indicates the specific stage or period an entity is in within an overall construction or building process.
-
C.
mainConstructionPhaseUnder
Indicates that one construction phase occurs under or is subordinate to another primary construction phase in a project’s timeline or hierarchy.
-
D.
capitalPhase
Indicates a relationship where an entity is in a particular stage or phase of capital development, investment, or funding.
-
E.
redevelopmentPhasing
Indicates the planned sequence and timing in which different parts of a redevelopment project are to be carried out.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:15 a.m.