Triple
T34532639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike VI |
E886581
|
entity |
| Predicate | subspeciesAncestry |
P179283
|
FINISHED |
| Object | Bengal tiger |
—
|
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: Bengal tiger | Statement: [Mike VI, subspeciesAncestry, Bengal tiger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subspeciesAncestry Context triple: [Mike VI, subspeciesAncestry, Bengal tiger]
-
A.
subspeciesOf
Indicates that one taxonomic group is a subspecific rank within, and directly derived from, another species.
-
B.
subspeciesIncludes
Indicates that a particular subspecies contains or encompasses the referenced member entities within its taxonomic grouping.
-
C.
ancestralSubgroups
Indicates that one group consists of or descends from earlier, foundational subgroups within a lineage or hierarchy.
-
D.
secondaryAncestry
Indicates a secondary or additional ancestral relationship that an entity has beyond its primary ancestry.
-
E.
subspeciesCommonName
Indicates the common (non-scientific) name used to refer to a particular subspecies.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:02 a.m.