Triple
T8726260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carduelinae |
E207137
|
entity |
| Predicate | notableFeedingBehavior |
P84287
|
FINISHED |
| Object | gregarious at feeding sites |
—
|
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: gregarious at feeding sites | Statement: [Carduelinae, notableFeedingBehavior, gregarious at feeding sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFeedingBehavior Context triple: [Carduelinae, notableFeedingBehavior, gregarious at feeding sites]
-
A.
feedingHabitat
Indicates the type of environment or location where an organism typically obtains and consumes its food.
-
B.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
-
C.
feedingSpecialization
Indicates a relationship where an entity is specialized or adapted to feed on a particular type or range of food resources.
-
D.
gnawingBehavior
Indicates a relationship where an entity persistently chews or bites another entity, typically causing gradual wear or damage.
-
E.
feederFoodPreference
Indicates the type of food that is preferred or typically used in a particular feeder.
- F. None of above. chosen
Provenance (4 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d158b0481908249610458f97306 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:36 p.m.