Triple
T26373564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taxidea |
E660832
|
entity |
| Predicate | hasMemberWithDiet |
P83089
|
FINISHED |
| Object | carnivorous |
—
|
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: carnivorous | Statement: [Taxidea, hasMemberWithDiet, carnivorous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberWithDiet Context triple: [Taxidea, hasMemberWithDiet, carnivorous]
-
A.
membersDiet
chosen
Indicates the type of diet that the members of a group, organization, or category typically follow or are characterized by.
-
B.
hasPositionInDiet
Indicates the relative role or ranking that something occupies within a diet or dietary plan.
-
C.
hasDietaryLaw
Indicates that one entity prescribes, follows, or is governed by a specific set of dietary rules or restrictions associated with another entity.
-
D.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
-
E.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 26, 2026, 11 p.m.