Triple
T16752651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cataglyphis |
E407121
|
entity |
| Predicate | navigationStrategy |
P8588
|
FINISHED |
| Object | path integration |
—
|
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: path integration | Statement: [Cataglyphis, navigationStrategy, path integration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationStrategy Context triple: [Cataglyphis, navigationStrategy, path integration]
-
A.
navigationType
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
B.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
C.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
D.
navigatesUsing
chosen
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
E.
navigationKey
Indicates a key or control used to move focus, selection, or position within an interface, document, or environment.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa282bb08190992c9b61caa7a345 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.