Triple
T20716052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Bounty (Klingon Bird-of-Prey) |
E509171
|
entity |
| Predicate | usedToTransport |
P115555
|
FINISHED |
| Object | two humpback whales |
—
|
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: two humpback whales | Statement: [HMS Bounty (Klingon Bird-of-Prey), usedToTransport, two humpback whales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToTransport Context triple: [HMS Bounty (Klingon Bird-of-Prey), usedToTransport, two humpback whales]
-
A.
commonlyTransportedIn
Indicates that something is usually carried, moved, or conveyed using a particular vehicle, container, or mode of transport.
-
B.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
C.
usedAsVehicleFor
chosen
Indicates that one entity functions as a means of transportation or conveyance for another entity.
-
D.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
E.
transportedFor
Indicates that one entity was moved or carried from one place to another for the benefit, use, or purpose of another entity or activity.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d1f3308190ae594a5b9e4ab9d5 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.