Triple
T3889143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMHS Britannic |
E88014
|
entity |
| Predicate | passengersOnFinalVoyage |
P881
|
FINISHED |
| Object | approximately 1,065 |
—
|
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: approximately 1,065 | Statement: [HMHS Britannic, passengersOnFinalVoyage, approximately 1,065]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengersOnFinalVoyage Context triple: [HMHS Britannic, passengersOnFinalVoyage, approximately 1,065]
-
A.
passengers
chosen
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
B.
totalPeopleOnBoard
Indicates the total number of people currently present on a given vehicle, vessel, or similar conveyance.
-
C.
fatalitiesOnboard
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
-
D.
crewSurvivorsOnReturn
Indicates that the members of a crew remained alive and successfully returned from a mission or journey.
-
E.
laterOutcomeOfVoyage
Indicates that one event, state, or outcome occurs as a subsequent result or later phase of a specified voyage.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecaee7148190ada451ccfc6582ee |
completed | March 9, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.