Triple
T20905038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utahraptor |
E514771
|
entity |
| Predicate | huntingAdaptation |
P31439
|
FINISHED |
| Object | enlarged retractable toe claw |
—
|
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: enlarged retractable toe claw | Statement: [Utahraptor, huntingAdaptation, enlarged retractable toe claw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: huntingAdaptation Context triple: [Utahraptor, huntingAdaptation, enlarged retractable toe claw]
-
A.
primarySenseForHunting
Indicates that the referenced sense (such as sight, smell, or hearing) is the main one an entity relies on for hunting.
-
B.
hunting
Indicates one entity actively pursuing and attempting to capture or kill another entity, typically as prey.
-
C.
secondarySenseForHunting
Indicates that an entity has a secondary sensory capability that is specifically used to aid in hunting.
-
D.
huntingStyle
chosen
Indicates the characteristic manner or method an entity typically uses when hunting.
-
E.
huntingTime
Indicates the time period during which a hunting activity takes place or is scheduled.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8ff36488190987ecdfcbed4220c |
completed | April 21, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.