Triple
T2547987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess |
E57949
|
entity |
| Predicate | voyageOutcome |
P21239
|
FINISHED |
| Object | successful return with prize cargo |
—
|
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: successful return with prize cargo | Statement: [Duchess, voyageOutcome, successful return with prize cargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voyageOutcome Context triple: [Duchess, voyageOutcome, successful return with prize cargo]
-
A.
laterOutcomeOfVoyage
Indicates that one event, state, or outcome occurs as a subsequent result or later phase of a specified voyage.
-
B.
crewOutcome
Indicates the result or status experienced by a crew as a consequence of an event, action, or condition.
-
C.
subsequentVoyage
Indicates that one voyage occurs after and in sequence to another voyage in time.
-
D.
voyageType
Indicates the specific category or nature of a journey or trip that an entity undertakes.
-
E.
missionOutcome
chosen
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2e672948190bb7fe9b47535a172 |
completed | March 7, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.