Triple
T15491858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Canary Wharf |
E378704
|
entity |
| Predicate | setDuringDoctorEra |
P93599
|
FINISHED |
| Object | Tenth Doctor era |
—
|
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: Tenth Doctor era | Statement: [Battle of Canary Wharf, setDuringDoctorEra, Tenth Doctor era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setDuringDoctorEra Context triple: [Battle of Canary Wharf, setDuringDoctorEra, Tenth Doctor era]
-
A.
associatedDoctorEra
Indicates a relationship where a doctor is linked to a specific historical or professional era in which they were active or relevant.
-
B.
functionDuringImperialEra
Indicates that a function, role, or activity occurred or was in effect during the imperial era.
-
C.
settingDepictedPeriod
chosen
Indicates the historical or temporal period in which the setting of something (e.g., a work or scene) is depicted.
-
D.
functionDuringReconstructionEra
Indicates that an entity performs or holds a particular function, role, or activity specifically during the Reconstruction Era.
-
E.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fac2af88190ac1d119e6b21dbe0 |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:49 a.m.