Triple
T29555340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epping Ongar Railway |
E749887
|
entity |
| Predicate | hasHeritageBuses |
P182241
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Epping Ongar Railway, hasHeritageBuses, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeritageBuses Context triple: [Epping Ongar Railway, hasHeritageBuses, yes]
-
A.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
B.
hasTrolleybusLine
Indicates that there exists a trolleybus service or route connecting the related entities.
-
C.
hasTrolleybusSystem
Indicates that an entity operates or is served by a trolleybus transportation system.
-
D.
hasTramcarsFrom
Indicates that a tramcar originates from, or is sourced from, a specified location or provider.
-
E.
hasBusType
Indicates that one entity (typically a bus or bus service) is associated with or classified by a specific type or category of bus.
- F. None of above. chosen
Provenance (4 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 28, 2026, 5:15 p.m.