Triple
T34770372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gelochelidon |
E1002345
|
entity |
| Predicate | hasForagingBehavior |
P10557
|
FINISHED |
| Object | hawking for insects |
—
|
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: hawking for insects | Statement: [Gelochelidon, hasForagingBehavior, hawking for insects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasForagingBehavior Context triple: [Gelochelidon, hasForagingBehavior, hawking for insects]
-
A.
hasForagingAbility
Indicates that an entity possesses the capability or skill to search for and obtain food or resources.
-
B.
foragingTendency
Indicates the degree to which an entity is inclined or likely to engage in searching for and gathering food or resources.
-
C.
foragingStratum
Indicates the vertical layer or height within a habitat where an organism typically searches for and obtains its food.
-
D.
foragingAssociation
Indicates a relationship where entities search for or obtain food in association with one another, typically sharing space, time, or coordination during foraging activities.
-
E.
foragingStrategy
chosen
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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 3, 2026, 3:59 p.m.