Triple
T8913794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chlorochrysa |
E212246
|
entity |
| Predicate | hasFeedingBehavior |
P84287
|
FINISHED |
| Object | primarily insectivorous |
—
|
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: primarily insectivorous | Statement: [Chlorochrysa, hasFeedingBehavior, primarily insectivorous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeedingBehavior Context triple: [Chlorochrysa, hasFeedingBehavior, primarily insectivorous]
-
A.
notableFeedingBehavior
chosen
Indicates a characteristic way or pattern in which an entity typically obtains or consumes food that is considered distinctive or noteworthy.
-
B.
feedingHabitat
Indicates the type of environment or location where an organism typically obtains and consumes its food.
-
C.
includesFeedingType
Indicates that one entity encompasses or specifies a particular type or category of feeding associated with another entity.
-
D.
feederFoodPreference
Indicates the type of food that is preferred or typically used in a particular feeder.
-
E.
feedingType
Indicates the manner or method by which one entity provides nourishment or food to another.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65276b788190ab76372d0d871fef |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.