Triple
T8756977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cronquist system |
E208094
|
entity |
| Predicate | originalProposalYear |
P25813
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Cronquist system, originalProposalYear, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalProposalYear Context triple: [Cronquist system, originalProposalYear, 1968]
-
A.
proposedInYear
chosen
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
-
B.
originallyProposedFor
Indicates that something was first suggested, designed, or intended to be used for a particular purpose, context, or target.
-
C.
originalPlannedLaunchYear
Indicates the year that was initially scheduled or intended for an entity’s launch before any delays or changes.
-
D.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
E.
firstPlanStartYear
Indicates the calendar year in which an entity’s initial plan or planning period begins.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ddabdc88190ba50ef1833a815d0 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.