Triple
T3284380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blakiston's fish owl |
E68944
|
entity |
| Predicate | huntingMethod |
P31439
|
FINISHED |
| Object | perches above water and strikes fish |
—
|
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: perches above water and strikes fish | Statement: [Blakiston's fish owl, huntingMethod, perches above water and strikes fish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: huntingMethod Context triple: [Blakiston's fish owl, huntingMethod, perches above water and strikes fish]
-
A.
huntingStyle
chosen
Indicates the characteristic manner or method an entity typically uses when hunting.
-
B.
hunting
Indicates one entity actively pursuing and attempting to capture or kill another entity, typically as prey.
-
C.
huntingTime
Indicates the time period during which a hunting activity takes place or is scheduled.
-
D.
preyCaptureMechanism
Indicates the method or strategy an organism uses to locate, seize, and secure its prey.
-
E.
usesForPreyCapture
Indicates that an entity employs another entity as a means or tool for capturing prey.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0377c9c819089af47952946de52 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.