Triple
T21831144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 90 |
E538996
|
entity |
| Predicate | buildDateRange |
P46071
|
FINISHED |
| Object | 1987–1990 |
—
|
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: 1987–1990 | Statement: [British Rail Class 90, buildDateRange, 1987–1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildDateRange Context triple: [British Rail Class 90, buildDateRange, 1987–1990]
-
A.
representsDateRange
chosen
Indicates that a subject is associated with, valid for, or applicable during a specific start-to-end date range.
-
B.
createdBetween
Indicates that something was created within a specified start and end time or date range.
-
C.
chronologicallyBetween
Indicates that one event or time point occurs after a first reference point and before a second reference point in temporal order.
-
D.
startDateAsGuerrilla
Indicates the date on which an entity began operating or acting in a guerrilla capacity.
-
E.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f091362d9081909f00ad7a2806d5cb |
completed | April 28, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.