Triple
T36508012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Plan |
E899821
|
entity |
| Predicate | successorAdoptedYear |
P33884
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Pacific Plan, successorAdoptedYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAdoptedYear Context triple: [Pacific Plan, successorAdoptedYear, 2014]
-
A.
successorAdoptionYear
chosen
Indicates the year in which a successor entity formally adopted or took over from its predecessor.
-
B.
successionYear
Indicates the calendar year in which one entity formally succeeded or took over from another in a given role, position, or status.
-
C.
originYearOfPredecessor
Indicates the calendar year in which the predecessor entity first originated or was established.
-
D.
successorEraStartYear
Indicates the calendar year in which the era that follows another era begins.
-
E.
dateOfSuccession
Indicates the specific date on which one entity formally succeeded or took over a role, position, or title from another.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0076c0a5c4819088b17b95511b93ed |
completed | May 10, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_6a007638a67c81909c091335142260ab |
completed | May 10, 2026, 12:12 p.m. |
Created at: May 3, 2026, 4:10 p.m.