Triple
T25922741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vannes Cathedral |
E653213
|
entity |
| Predicate | hasEarlierStructureFrom |
P50156
|
FINISHED |
| Object | 11th century |
—
|
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: 11th century | Statement: [Vannes Cathedral, hasEarlierStructureFrom, 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlierStructureFrom Context triple: [Vannes Cathedral, hasEarlierStructureFrom, 11th century]
-
A.
hasPredecessorStructureFrom
chosen
Indicates that one structure existed or was established before another structure in a sequential or developmental order.
-
B.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
C.
hasEarlierVersion
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
-
D.
containsStructureFrom
Indicates that one entity includes or incorporates a structural component originating from another entity.
-
E.
hasEarlierPhase
Indicates that one phase occurs before another phase in a process or sequence.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603ea6ea081909c6223c5544f6992 |
completed | May 2, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:32 a.m.