Triple
T367511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Beagle second survey expedition |
E7993
|
entity |
| Predicate | sequenceInBeagleVoyages |
P11678
|
FINISHED |
| Object | second voyage |
—
|
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 | Statement: [HMS Beagle second survey expedition, sequenceInBeagleVoyages, second voyage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceInBeagleVoyages Context triple: [HMS Beagle second survey expedition, sequenceInBeagleVoyages, second voyage]
-
A.
sisterBeaches
Indicates a relationship between two beaches where they are considered counterparts or closely linked, often due to similarities, proximity, or a formal pairing.
-
B.
voyageStartYearDescribed
Indicates the year in which a voyage is described as having started.
-
C.
codenameOfLandings
Indicates that one entity is the codename assigned to a specific set of landings or landing operations.
-
D.
followsCoast
Indicates that one entity’s path or boundary runs alongside and generally conforms to the shape of a coastline.
-
E.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe92c7c8190b49af2b2b461eacc |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0b23ec8190bef9d593162388a4 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.