Triple
T6096176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Succulent Karoo |
E135882
|
entity |
| Predicate | hasFaunaGroup |
P68099
|
FINISHED |
| Object | reptiles |
—
|
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: reptiles | Statement: [Succulent Karoo, hasFaunaGroup, reptiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFaunaGroup Context triple: [Succulent Karoo, hasFaunaGroup, reptiles]
-
A.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
B.
hasZoo
Indicates that one entity possesses, operates, or is associated with a zoo.
-
C.
hasLakeGroup
Indicates that an entity possesses, contains, or is associated with a specific group or collection of lakes.
-
D.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
E.
hasPhylum
Indicates that an entity (typically a biological taxon or organism) is classified as belonging to a particular phylum in a taxonomic hierarchy.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a9764048190ad4e9a02f9a25ab6 |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:12 p.m.