Triple
T11584251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Beagle |
E274709
|
entity |
| Predicate | famousVoyage |
P100443
|
FINISHED |
| Object | second voyage (1831–1836) |
—
|
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: second voyage (1831–1836) | Statement: [HMS Beagle, famousVoyage, second voyage (1831–1836)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousVoyage Context triple: [HMS Beagle, famousVoyage, second voyage (1831–1836)]
-
A.
firstCircumnavigation
Indicates that the subject is responsible for completing the first full circumnavigation of the Earth (or another specified body or area).
-
B.
sponsoredVoyagesOf
Indicates that one entity provided financial or logistical support for the voyages undertaken by another entity.
-
C.
voyageOn
Indicates that an entity is traveling or being transported aboard a particular vessel or means of sea (or space) travel.
-
D.
purposeOfVoyages
Indicates the intended goals, reasons, or objectives motivating or justifying specific voyages.
-
E.
firstToLand
Indicates that the subject is the earliest or initial entity to arrive at or touch down on a particular place or surface.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8904db5748190ae5f10ae86ccdf46 |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.