Triple
T32019764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kopeka |
E817647
|
entity |
| Predicate | navigatesIn |
P36970
|
FINISHED |
| Object | dark caves |
—
|
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: dark caves | Statement: [Kopeka, navigatesIn, dark caves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigatesIn Context triple: [Kopeka, navigatesIn, dark caves]
-
A.
navigatedIn
chosen
Indicates that an entity moved or steered through or within a particular medium, environment, or space.
-
B.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
C.
navigatedBy
Indicates that the movement, direction, or operation of something is controlled, guided, or steered by a specified agent.
-
D.
navigableTo
Indicates that one entity can be reached or traversed to from another entity, typically following valid paths or connections within a system or environment.
-
E.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b465db6881908f0c0758d884c376 |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:16 a.m.