Triple
T3391444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Venture |
E71427
|
entity |
| Predicate | passengersSubsequentAction |
P49362
|
FINISHED |
| Object | built the pinnace Deliverance in Bermuda |
—
|
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: built the pinnace Deliverance in Bermuda | Statement: [Sea Venture, passengersSubsequentAction, built the pinnace Deliverance in Bermuda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengersSubsequentAction Context triple: [Sea Venture, passengersSubsequentAction, built the pinnace Deliverance in Bermuda]
-
A.
passengers
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
B.
nextShuttleFlightAfterDisaster
Indicates the first shuttle flight that took place after a specified disaster event.
-
C.
subsequentVoyage
Indicates that one voyage occurs after and in sequence to another voyage in time.
-
D.
formerPassengerService
Indicates that an entity previously provided passenger transportation services but no longer does so.
-
E.
destinationOfFlight
Indicates the location or place to which a given flight is traveling or scheduled to arrive.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb850594c81909b6f8a384fc98cb2 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb2e426b88190b82d9830149b142e |
completed | March 8, 2026, 5:33 p.m. |
Created at: March 8, 2026, 3:14 p.m.