Triple
T4019294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heslington East |
E91240
|
entity |
| Predicate | firstPhaseOpeningYear |
P2467
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Heslington East, firstPhaseOpeningYear, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPhaseOpeningYear Context triple: [Heslington East, firstPhaseOpeningYear, 2009]
-
A.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
B.
officialOpeningYear
chosen
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
C.
firstLineOpeningDate
Indicates the date on which the first line in a system, network, or service was officially opened or began operation.
-
D.
firstYear
Indicates that an entity is in its first year of existence, operation, or participation within a specified context.
-
E.
firstSeriesYear
Indicates the year in which a series (such as a TV show, book series, or sports league season) first began or was initially released.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaab39d4819080e37cd175c89542 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.