Triple
T26406591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebastián Vizcaíno |
E663849
|
entity |
| Predicate | purposeOfExpedition |
P24308
|
FINISHED |
| Object | detailed mapping of the California coast |
—
|
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: detailed mapping of the California coast | Statement: [Sebastián Vizcaíno, purposeOfExpedition, detailed mapping of the California coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfExpedition Context triple: [Sebastián Vizcaíno, purposeOfExpedition, detailed mapping of the California coast]
-
A.
expeditionObjective
chosen
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
B.
purposeOfVoyages
Indicates the intended goals, reasons, or objectives motivating or justifying specific voyages.
-
C.
explorationPurpose
Indicates that an entity is engaged in or associated with an activity whose primary goal is exploration or discovery.
-
D.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
E.
describesExpedition
Indicates that one entity provides a detailed account or characterization of an expedition undertaken by another entity.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 11:35 p.m.