Triple
T20999859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dromaeosaurus |
E517255
|
entity |
| Predicate | likelyHuntingStrategy |
P31439
|
FINISHED |
| Object | active predation on small to medium-sized vertebrates |
—
|
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: active predation on small to medium-sized vertebrates | Statement: [Dromaeosaurus, likelyHuntingStrategy, active predation on small to medium-sized vertebrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyHuntingStrategy Context triple: [Dromaeosaurus, likelyHuntingStrategy, active predation on small to medium-sized vertebrates]
-
A.
isHuntedBy
Indicates that one entity is the target of hunting activity carried out by another entity.
-
B.
associatedWithHunting
Indicates a relationship where an entity is connected to, involved in, or commonly linked with the activity or practice of hunting.
-
C.
huntingStyle
chosen
Indicates the characteristic manner or method an entity typically uses when hunting.
-
D.
huntingTime
Indicates the time period during which a hunting activity takes place or is scheduled.
-
E.
foragingStrategy
Indicates the method or pattern an organism uses to search for, obtain, and exploit food resources.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc24a6dc8190a6bf81cf1d9590c0 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:51 p.m.