Triple
T7577303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetanurae |
E179390
|
entity |
| Predicate | includesMembersWithDiet |
P28386
|
FINISHED |
| Object | 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: omnivorous | Statement: [Tetanurae, includesMembersWithDiet, omnivorous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMembersWithDiet Context triple: [Tetanurae, includesMembersWithDiet, omnivorous]
-
A.
includesSpeciesWithDiet
chosen
Indicates that a group, area, or collection contains at least one species characterized by a specified type of diet.
-
B.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
C.
dietaryOptions
Indicates the types of diets or food-related preferences, restrictions, or choices that are applicable to or offered for an entity.
-
D.
characterizesDietAs
Indicates that one entity describes, defines, or assigns the type or nature of another entity’s diet.
-
E.
hasDietaryLaw
Indicates that one entity prescribes, follows, or is governed by a specific set of dietary rules or restrictions associated with 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f94cdbec81909f2ba7ce04e49931 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.