Triple
T26372250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Russell |
E660804
|
entity |
| Predicate | navigationChartedBy |
P91962
|
FINISHED |
| Object | Admiralty charts |
—
|
NE NERFINISHED |
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: Admiralty charts | Statement: [Little Russell, navigationChartedBy, Admiralty charts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationChartedBy Context triple: [Little Russell, navigationChartedBy, Admiralty charts]
-
A.
navigationOutput
Indicates that an entity produces or provides navigational information or guidance as an output to another entity or system.
-
B.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
C.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
D.
navigationProblemAddressed
Indicates that a navigation-related issue, obstacle, or challenge has been identified and dealt with or resolved.
-
E.
hasNavigationChart
chosen
Indicates that an entity possesses or is associated with a navigation chart used for guiding travel or movement.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6103043288190b762b7e1eda5a46b |
completed | May 2, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:59 p.m.