Triple
T19109679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford Tube coaches |
E467752
|
entity |
| Predicate | ownedFleet |
P134445
|
FINISHED |
| Object | high-capacity coaches |
—
|
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: high-capacity coaches | Statement: [Oxford Tube coaches, ownedFleet, high-capacity coaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedFleet Context triple: [Oxford Tube coaches, ownedFleet, high-capacity coaches]
-
A.
usesFleetOf
Indicates that one entity operates or relies on a group of vehicles, vessels, or similar assets collectively as a fleet to perform its activities or services.
-
B.
belongsToFleet
Indicates that an entity is a member of, or is assigned to, a specific fleet or group of vehicles/vessels.
-
C.
ownsService
Indicates that one entity has ownership or control over a particular service.
-
D.
hasSubfleet
Indicates that one fleet entity contains or manages another fleet entity as a subordinate or component fleet.
-
E.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e392ef488190a230b1d2890b2a9d |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.