Triple
T38494574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accipiter poliogaster |
E919653
|
entity |
| Predicate | hasFootType |
P12848
|
FINISHED |
| Object | raptorial talons |
—
|
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: raptorial talons | Statement: [Accipiter poliogaster, hasFootType, raptorial talons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFootType Context triple: [Accipiter poliogaster, hasFootType, raptorial talons]
-
A.
footType
chosen
Indicates the specific kind or classification of feet that an entity possesses or is characterized by.
-
B.
hasFootName
Indicates that an entity has a foot (or feet) identified by a specific name.
-
C.
hasHeelType
Indicates that an item (typically footwear) possesses a specific type or style of heel.
-
D.
hasFootUsed
Indicates that an entity uses a particular foot (or feet) to perform an action or function.
-
E.
hasFootPatternVariant
Indicates a relationship where an entity possesses a specific variant of a foot pattern distinct from other possible foot pattern types.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 3, 2026, 4:31 p.m.