Triple
T9752592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosie |
E236475
|
entity |
| Predicate | speciesGroup |
P16820
|
FINISHED |
| Object | insects and arthropods of A Bug's Life |
—
|
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: insects and arthropods of A Bug's Life | Statement: [Rosie, speciesGroup, insects and arthropods of A Bug's Life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesGroup Context triple: [Rosie, speciesGroup, insects and arthropods of A Bug's Life]
-
A.
speciesType
Indicates the specific biological species category to which an entity belongs.
-
B.
taxonGroup
chosen
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
C.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
D.
speciesForm
Indicates that one entity is a specific biological form, variant, or manifestation of a species represented by another entity.
-
E.
typeSpecies
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
- 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_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fae332c8190b11f0258b5a5ae2b |
completed | April 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.