Triple
T10903566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sinking of the RMS Lusitania |
E257507
|
entity |
| Predicate | voyageNumber |
P96323
|
FINISHED |
| Object | 202nd transatlantic crossing |
—
|
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: 202nd transatlantic crossing | Statement: [sinking of the RMS Lusitania, voyageNumber, 202nd transatlantic crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voyageNumber Context triple: [sinking of the RMS Lusitania, voyageNumber, 202nd transatlantic crossing]
-
A.
voyageOn
Indicates that an entity is traveling or being transported aboard a particular vessel or means of sea (or space) travel.
-
B.
voyageType
Indicates the specific category or nature of a journey or trip that an entity undertakes.
-
C.
voyageWith
Indicates that two or more entities travel together on the same journey or trip, sharing a common route or voyage.
-
D.
organizedVoyage
Indicates that one entity planned, arranged, or coordinated the details of a journey or trip undertaken by another entity.
-
E.
subsequentVoyage
Indicates that one voyage occurs after and in sequence to another voyage in time.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d761a5dffc8190927b0928978646a4 |
completed | April 9, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:22 p.m.