Triple
T22798674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PacificCoastNavigation |
E564320
|
entity |
| Predicate | usesInformationSource |
P26860
|
FINISHED |
| Object | sailing directions |
—
|
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: sailing directions | Statement: [PacificCoastNavigation, usesInformationSource, sailing directions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInformationSource Context triple: [PacificCoastNavigation, usesInformationSource, sailing directions]
-
A.
usesInformationSources
chosen
Indicates that an entity relies on or consults specified information sources to perform actions, make decisions, or obtain knowledge.
-
B.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
C.
intelligenceSource
Indicates that one entity serves as the origin or provider of intelligence information for another entity.
-
D.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
E.
usesSourceCatalogues
Indicates that one entity relies on or references source catalogues as the basis for its data, operations, or decisions.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cdb6ba48190936bd356704c1241 |
completed | April 29, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.