Triple
T11894605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verney Junction |
E283003
|
entity |
| Predicate | goodsServicesEnded |
P84963
|
FINISHED |
| Object | 1964-09-06 |
—
|
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: 1964-09-06 | Statement: [Verney Junction, goodsServicesEnded, 1964-09-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goodsServicesEnded Context triple: [Verney Junction, goodsServicesEnded, 1964-09-06]
-
A.
serviceEnded
chosen
Indicates that a previously active service or service relationship has come to an end.
-
B.
hasGoodsServices
Indicates that one entity provides, offers, or is associated with specific goods or services in relation to another entity.
-
C.
originalServiceEnded
Indicates that a previously existing or initial service has come to an end or has been terminated.
-
D.
salesEnd
Indicates the point in time or condition at which a sales period or selling activity is concluded or no longer valid.
-
E.
activityEndedBecauseOf
Indicates that an activity has come to an end specifically due to a particular cause, condition, or event.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1172988190a2c13d37220f2f93 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.