Triple
T25750614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InSight |
E648459
|
entity |
| Predicate | proposalSelectionYear |
P21538
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [InSight, proposalSelectionYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposalSelectionYear Context triple: [InSight, proposalSelectionYear, 2012]
-
A.
selectionYear
chosen
Indicates the year in which an entity was chosen or selected for a particular role, status, or inclusion.
-
B.
promotionYear
Indicates the year in which an entity was promoted to a new position, rank, or status.
-
C.
campaignYear
Indicates the specific year in which a campaign takes place, is launched, or is associated with an entity.
-
D.
awardSelectionBy
Indicates that an award or honor was chosen or determined by a particular person, group, or organization.
-
E.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 22, 2026, 4:34 a.m.