Triple
T26697231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GO TO 2040 comprehensive regional plan |
E673054
|
entity |
| Predicate | planningPeriodStartYear |
P113284
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [GO TO 2040 comprehensive regional plan, planningPeriodStartYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningPeriodStartYear Context triple: [GO TO 2040 comprehensive regional plan, planningPeriodStartYear, 2010]
-
A.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
B.
planningStartYear
chosen
Indicates the calendar year in which planning for an activity, project, or process begins.
-
C.
firstPlanStartYear
Indicates the calendar year in which an entity’s initial plan or planning period begins.
-
D.
plannedEndYear
Indicates the calendar year in which an activity, project, or plan is intended or scheduled to be completed.
-
E.
eligibilityPeriodStartYear
Indicates the calendar year in which an entity’s eligibility 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 3:29 a.m.