Triple
T27741194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manucodia |
E701857
|
entity |
| Predicate | hasFeedingEcology |
P84287
|
FINISHED |
| Object | fruit and small animals |
—
|
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: fruit and small animals | Statement: [Manucodia, hasFeedingEcology, fruit and small animals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeedingEcology Context triple: [Manucodia, hasFeedingEcology, fruit and small animals]
-
A.
hasEcology
Indicates that an entity has a particular ecological context, such as its habitat, environmental role, or interactions within an ecosystem.
-
B.
feedingHabitat
Indicates the type of environment or location where an organism typically obtains and consumes its food.
-
C.
notableFeedingBehavior
chosen
Indicates a characteristic way or pattern in which an entity typically obtains or consumes food that is considered distinctive or noteworthy.
-
D.
isMajorFoodSourceFor
Indicates that something serves as a primary or significant source of food for another entity.
-
E.
trophicType
Indicates the way an organism obtains its energy and nutrients within a food web or ecosystem.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 4:11 p.m.