Triple
T26996187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macaca |
E679984
|
entity |
| Predicate | notableSpeciesForResearch |
P138207
|
FINISHED |
| Object | Macaca mulatta |
—
|
NE NERFINISHED |
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: Macaca mulatta | Statement: [Macaca, notableSpeciesForResearch, Macaca mulatta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSpeciesForResearch Context triple: [Macaca, notableSpeciesForResearch, Macaca mulatta]
-
A.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
B.
notableCreatureStudied
chosen
Indicates that a particular creature has been the subject of significant study or research by the referenced entity.
-
C.
notableSpeciesRole
Indicates that a species plays a particularly important, characteristic, or influential role in relation to another entity or context.
-
D.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
E.
habitatOfNotableSpecies
Indicates that a location serves as the natural environment or living area for one or more notable species.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: April 27, 2026, 6:54 a.m.