Triple
T1018302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Half Moon |
E21981
|
entity |
| Predicate | purposeOfVoyage |
P15346
|
FINISHED |
| Object | search for a northeast passage to Asia |
—
|
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: search for a northeast passage to Asia | Statement: [Half Moon, purposeOfVoyage, search for a northeast passage to Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfVoyage Context triple: [Half Moon, purposeOfVoyage, search for a northeast passage to Asia]
-
A.
purposeOfVoyages
chosen
Indicates the intended goals, reasons, or objectives motivating or justifying specific voyages.
-
B.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
C.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
D.
voyageOriginCountry
Indicates the country from which a voyage departs or originates.
-
E.
usesAtSea
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c6005081909d9e56114c532d14 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.