Triple
T4111986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphibia |
E90196
|
entity |
| Predicate | larvalDiet |
P15763
|
FINISHED |
| Object | often herbivorous or omnivorous |
—
|
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: often herbivorous or omnivorous | Statement: [Amphibia, larvalDiet, often herbivorous or omnivorous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: larvalDiet Context triple: [Amphibia, larvalDiet, often herbivorous or omnivorous]
-
A.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
-
B.
hasLarvalFeature
chosen
Indicates that an entity possesses a characteristic or trait specifically associated with its larval developmental stage.
-
C.
trophicType
Indicates the way an organism obtains its energy and nutrients within a food web or ecosystem.
-
D.
includesSpeciesWithDiet
Indicates that a group, area, or collection contains at least one species characterized by a specified type of diet.
-
E.
primaryFood
Indicates that one entity serves as the main or most important food source for another entity.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.