Triple
T8934459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Great Circle route |
E212739
|
entity |
| Predicate | navigatedUsing |
P11421
|
FINISHED |
| Object | spherical trigonometry |
—
|
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: spherical trigonometry | Statement: [Pacific Great Circle route, navigatedUsing, spherical trigonometry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigatedUsing Context triple: [Pacific Great Circle route, navigatedUsing, spherical trigonometry]
-
A.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
B.
navigatedIn
Indicates that an entity moved or steered through or within a particular medium, environment, or space.
-
C.
navigatedBy
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
-
D.
usedToNavigate
chosen
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
E.
navigatedAround
Indicates that one entity moved in such a way as to go past or circumvent another entity or obstacle without directly passing through or over it.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc669138b48190a6bb4968f029a69e |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:58 p.m.