Triple
T21187292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BFC 1909 |
E522113
|
entity |
| Predicate | hasYearInName |
P33319
|
FINISHED |
| Object | 1909 |
—
|
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: 1909 | Statement: [BFC 1909, hasYearInName, 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYearInName Context triple: [BFC 1909, hasYearInName, 1909]
-
A.
hasYearInTitle
chosen
Indicates that the title of an entity explicitly contains a year value as part of its text.
-
B.
hasTypeOfYear
Indicates that a given year is classified as belonging to a specific type or category of year (e.g., fiscal, academic, leap).
-
C.
wasNamedInYear
Indicates that an entity received or was given its name in a specific year.
-
D.
lastEditionYearUnderThisName
Indicates the final year in which something (such as a publication, event, or product) was issued or held under a specific name before that name changed or was discontinued.
-
E.
usedNameToYear
Indicates that a particular name was in use or valid during a specified year.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7302222788190aa55ee0ed7342498 |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.