Triple
T3856011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria (ship) |
E90015
|
entity |
| Predicate | firstCircumnavigation |
P52370
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Victoria (ship), firstCircumnavigation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCircumnavigation Context triple: [Victoria (ship), firstCircumnavigation, yes]
-
A.
firstChartedOn
Indicates that an entity was first mapped, recorded, or charted on a specific date or during a specific time.
-
B.
firstVoyageEndYear
Indicates the calendar year in which an entity’s first voyage or initial journey was completed or came to an end.
-
C.
startTimeOfCircumnavigation
Indicates the specific time at which a circumnavigation event begins.
-
D.
firstVoyageDestination
Indicates the location that an entity traveled to as the endpoint of its first voyage.
-
E.
firstCrewedMission
Indicates that the mission is the first instance in which humans were onboard or directly participated as crew.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec07d45081909b8f3e35eb710f4c |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:19 p.m.