Triple
T16384718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Mail Lines |
E397890
|
entity |
| Predicate | fleetUsedFor |
P72672
|
FINISHED |
| Object | emigrant transport |
—
|
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: emigrant transport | Statement: [Royal Mail Lines, fleetUsedFor, emigrant transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetUsedFor Context triple: [Royal Mail Lines, fleetUsedFor, emigrant transport]
-
A.
fleetIncludes
Indicates that a particular fleet contains or is composed of the specified entity or entities as its members.
-
B.
aircraftUsedFromFleetOf
Indicates that a specific aircraft is selected and used from a particular fleet of aircraft.
-
C.
usesFleetOf
chosen
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.
-
D.
engineUsedIn
Indicates that a particular engine is utilized as a component or power source within a specified system, device, or application.
-
E.
referredAircraftUsedFor
Indicates that the referenced aircraft is utilized for a particular purpose, role, or operation in relation to another entity or context.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3263c60088190b85a8c02bc3ef315 |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.