Triple
T29265989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NS SLT |
E741976
|
entity |
| Predicate | belongsToOperatorFleet |
P66365
|
FINISHED |
| Object | NS Sprinter fleet |
—
|
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: NS Sprinter fleet | Statement: [NS SLT, belongsToOperatorFleet, NS Sprinter fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToOperatorFleet Context triple: [NS SLT, belongsToOperatorFleet, NS Sprinter fleet]
-
A.
belongsToFleet
chosen
Indicates that an entity is a member of, or is assigned to, a specific fleet or group of vehicles/vessels.
-
B.
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.
-
C.
hasSubfleet
Indicates that one fleet entity contains or manages another fleet entity as a subordinate or component fleet.
-
D.
ownedFleet
Indicates that one entity possesses or controls a group of vehicles, vessels, or similar assets as its fleet.
-
E.
supportedFleet
Indicates that one entity provided assistance, resources, or services to sustain or enable the operations of a fleet.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 28, 2026, 12:45 p.m.