Triple
T36881144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandion haliaetus japonicus |
E911480
|
entity |
| Predicate | footAdaptation |
P106635
|
FINISHED |
| Object | reversible outer toe |
—
|
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: reversible outer toe | Statement: [Pandion haliaetus japonicus, footAdaptation, reversible outer toe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footAdaptation Context triple: [Pandion haliaetus japonicus, footAdaptation, reversible outer toe]
-
A.
footMorphologySuggests
Indicates that the structure or shape of a foot provides evidence or clues pointing toward a particular characteristic, behavior, or classification.
-
B.
footType
Indicates the specific kind or classification of feet that an entity possesses or is characterized by.
-
C.
performedOnFoot
Indicates that an action or activity was carried out while walking or traveling on foot rather than using a vehicle or other means of transport.
-
D.
hasFootUsed
Indicates that an entity uses a particular foot (or feet) to perform an action or function.
-
E.
feetFeature
chosen
Indicates that one entity has a specific characteristic, attribute, or notable aspect related to its feet.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd69b4b08190970609a0c2c3651a |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.