Triple
T249994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pan troglodytes |
E5120
|
entity |
| Predicate | cognitiveAbilities |
P750
|
FINISHED |
| Object | self-recognition in mirrors |
—
|
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: self-recognition in mirrors | Statement: [Pan troglodytes, cognitiveAbilities, self-recognition in mirrors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cognitiveAbilities Context triple: [Pan troglodytes, cognitiveAbilities, self-recognition in mirrors]
-
A.
intellectualTrend
Indicates a relationship where an idea, movement, or way of thinking is recognized as an intellectual trend influencing thought or discourse.
-
B.
assessmentMethod
chosen
Indicates the method or procedure used to evaluate, measure, or judge something.
-
C.
educatedIn
Indicates that an entity received education or formal training at a specified institution or place.
-
D.
fieldOfRecognition
Indicates the domain, discipline, or area in which an entity is formally acknowledged, honored, or recognized.
-
E.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d3728f0819086214ccc2db2305a |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.