Triple
T16030674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caretta caretta |
E388836
|
entity |
| Predicate | navigationMechanism |
P34226
|
FINISHED |
| Object | geomagnetic orientation |
—
|
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: geomagnetic orientation | Statement: [Caretta caretta, navigationMechanism, geomagnetic orientation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationMechanism Context triple: [Caretta caretta, navigationMechanism, geomagnetic orientation]
-
A.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
B.
navigationType
chosen
Indicates the method or mode by which movement or traversal is carried out between locations or through an environment.
-
C.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
D.
navigationSystemComponent
Indicates that one entity functions as a component or subpart of a navigation system associated with another entity.
-
E.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.