Triple
T16286221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrmecia |
E395393
|
entity |
| Predicate | navigationAbility |
P12979
|
FINISHED |
| Object | visual navigation |
—
|
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: visual navigation | Statement: [Myrmecia, navigationAbility, visual navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationAbility Context triple: [Myrmecia, navigationAbility, visual navigation]
-
A.
navigation
chosen
Indicates the act or process of determining and following a path or route from one location or state to another.
-
B.
navigationProblemAddressed
Indicates that a navigation-related issue, obstacle, or challenge has been identified and dealt with or resolved.
-
C.
navigationOutput
Indicates that an entity produces or provides navigational information or guidance as an output to another entity or system.
-
D.
navigationEnvironment
Indicates the contextual conditions or surroundings in which navigation or movement from one place to another occurs.
-
E.
navigationLockUse
Indicates the use or operation of a navigation lock by or for an entity, typically to enable passage through a controlled waterway segment.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24914bda08190a5d6315414ee3f76 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.