Triple
T26261122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epping (1959) |
E656848
|
entity |
| Predicate | serviceTypeEnabled |
P849
|
FINISHED |
| Object | suburban electric multiple unit services |
—
|
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: suburban electric multiple unit services | Statement: [Epping (1959), serviceTypeEnabled, suburban electric multiple unit services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceTypeEnabled Context triple: [Epping (1959), serviceTypeEnabled, suburban electric multiple unit services]
-
A.
serviceIs
Indicates that one entity functions as a service of a specified type or category in relation to another entity.
-
B.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
C.
serviceEnableVariablePattern
Indicates that a service can be enabled or configured according to a specified variable-based pattern.
-
D.
enablesService
Indicates that one entity provides the capability or necessary conditions for another entity to offer or perform a specific service.
-
E.
serviceAvailability
Indicates whether a particular service is accessible and operational for use during a given time or under specified conditions.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 9:10 p.m.