Triple
T3787586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Era |
E85564
|
entity |
| Predicate | doesNotIncludeYear |
P51525
|
FINISHED |
| Object | year 0 |
—
|
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: year 0 | Statement: [Common Era, doesNotIncludeYear, year 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotIncludeYear Context triple: [Common Era, doesNotIncludeYear, year 0]
-
A.
deprecatedYear
Indicates the year in which something (such as a feature, standard, or item) was officially marked as deprecated or no longer recommended for use.
-
B.
hasLetterNumberInYear
Indicates that a specific letter or document is assigned a particular sequential number within a given year.
-
C.
doesNotConsider
Indicates that one entity fails or chooses not to take another entity or factor into account when forming judgments, decisions, or actions.
-
D.
doesNotApplyRetroactivelyTo
Indicates that a rule, law, or condition does not affect events, actions, or situations that occurred before it came into effect.
-
E.
hasTypeOfYear
Indicates that a given year is classified as belonging to a specific type or category of year (e.g., fiscal, academic, leap).
- F. None of above. chosen
Provenance (4 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
| PDg | Predicate description generation | batch_69aee633dab88190b14cec8afb19ca6a |
completed | March 9, 2026, 3:24 p.m. |
Created at: March 9, 2026, 3:13 p.m.