Triple
T10774304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peregrine falcon |
E254158
|
entity |
| Predicate | huntingDiveSpeed |
P64307
|
FINISHED |
| Object | >200 miles per hour |
—
|
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: >200 miles per hour | Statement: [Peregrine falcon, huntingDiveSpeed, >200 miles per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: huntingDiveSpeed Context triple: [Peregrine falcon, huntingDiveSpeed, >200 miles per hour]
-
A.
diveSpeed
chosen
Indicates the speed at which an entity moves downward or descends, typically through a fluid such as air or water.
-
B.
divingBehavior
Indicates the characteristic way an entity performs or exhibits diving actions, such as how, when, or how often it dives.
-
C.
speedSubmerged
Indicates the speed at which an entity moves while it is submerged in a fluid, typically underwater.
-
D.
hasDivingComponent
Indicates that an activity, event, or process includes or involves a diving-related element or action.
-
E.
hasDiveType
Indicates that an entity performs or is associated with a specific type or category of dive.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7329be784819083b7ec4d85c20acf |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.