Triple
T13284454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of Burgos |
E316406
|
entity |
| Predicate | finalCompletion |
P1574
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Cathedral of Burgos, finalCompletion, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalCompletion Context triple: [Cathedral of Burgos, finalCompletion, 18th century]
-
A.
closureCompleted
Indicates that a previously initiated closure process or shutdown has been fully and successfully completed.
-
B.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
C.
completedIn
chosen
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
D.
finished
Indicates that an entity has completed an action, process, or state, reaching its end point.
-
E.
finish
Indicates that an entity brings an action, process, or state to an end or completion.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.