Triple
T13603075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instinct |
E324990
|
entity |
| Predicate | featuresNonHumanPrimates |
P62520
|
FINISHED |
| Object | gorillas |
—
|
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: gorillas | Statement: [Instinct, featuresNonHumanPrimates, gorillas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresNonHumanPrimates Context triple: [Instinct, featuresNonHumanPrimates, gorillas]
-
A.
hasPrimate
Indicates that one entity possesses, contains, or is associated with a primate.
-
B.
currentPrimate
Indicates that an entity is presently serving as the primary or leading figure (e.g., head or chief) within a specified organization, group, or context.
-
C.
previousPrimate
Indicates that one primate precedes another primate in a defined sequence, order, or lineage.
-
D.
physicalCharacteristics
chosen
Indicates that one entity has or describes the bodily or material attributes, features, or appearance of another entity.
-
E.
hasCurrentPrimate
Indicates that an entity currently has a specific primate associated with it, such as in a role, position, or status.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.