Triple
T17298510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Queen Mary |
E419973
|
entity |
| Predicate | returnedToPassengerService |
P107520
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [RMS Queen Mary, returnedToPassengerService, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToPassengerService Context triple: [RMS Queen Mary, returnedToPassengerService, 1947]
-
A.
openedAsPassengerService
chosen
Indicates that a transportation facility or route began operating specifically for carrying passengers.
-
B.
returnedVia
Indicates that something was sent back or responded to through a specified medium, channel, or method.
-
C.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
-
D.
formerPassengerService
Indicates that an entity previously provided passenger transportation services but no longer does so.
-
E.
returnedToFlightStatus
Indicates that an entity previously grounded, inactive, or suspended has been restored to an approved or operational flight status.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438f82788819088ea796850552297 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:41 a.m.