Triple
T10881447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giraffe Encounter |
E256928
|
entity |
| Predicate | animalDietProvided |
P96215
|
FINISHED |
| Object | zoo-approved giraffe food |
—
|
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: zoo-approved giraffe food | Statement: [Giraffe Encounter, animalDietProvided, zoo-approved giraffe food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animalDietProvided Context triple: [Giraffe Encounter, animalDietProvided, zoo-approved giraffe food]
-
A.
includesSpeciesWithDiet
Indicates that a group, area, or collection contains at least one species characterized by a specified type of diet.
-
B.
isHerbivorousOrOmnivorous
Indicates that an entity either primarily eats plants (herbivorous) or consumes both plant and animal matter (omnivorous).
-
C.
isCarnivorous
Indicates that an entity feeds primarily or exclusively on other animals.
-
D.
edibleSpecies
Indicates that one species can be safely eaten as food by another species or by humans.
-
E.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751da559c819094c3680a9f734ee7 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.