Triple
T2833535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Bellerophon |
E62295
|
entity |
| Predicate | tookToDestination |
P33653
|
FINISHED |
| Object | Napoleon Bonaparte to Plymouth |
—
|
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: Napoleon Bonaparte to Plymouth | Statement: [HMS Bellerophon, tookToDestination, Napoleon Bonaparte to Plymouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookToDestination Context triple: [HMS Bellerophon, tookToDestination, Napoleon Bonaparte to Plymouth]
-
A.
wentTo
Indicates that one entity traveled or moved from its original location to another specified place.
-
B.
carriedTo
chosen
Indicates that one entity transported or conveyed another entity from one place to another.
-
C.
wentToDistance
Indicates that an entity traveled to or reached a specified distance from a reference point.
-
D.
directedTo
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
-
E.
broughtTo
Indicates that one entity caused another entity or object to be transported or accompanied to a particular destination or recipient.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdec036dc8190bc2d974f6d82eda9 |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.