Triple
T1526316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo sapiens |
E32342
|
entity |
| Predicate | cognitiveAbility |
P8715
|
FINISHED |
| Object | planning |
—
|
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: planning | Statement: [Homo sapiens, cognitiveAbility, planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cognitiveAbility Context triple: [Homo sapiens, cognitiveAbility, planning]
-
A.
hasCognitiveComponent
Indicates that the related entity or process involves or depends on mental activities such as thinking, reasoning, perception, or understanding.
-
B.
typeOfIntelligence
Indicates that one entity is a specific kind or category of intelligence in relation to another entity.
-
C.
ability
chosen
Indicates that an entity has the capacity or power to perform a particular action or achieve a specific outcome.
-
D.
competence
Indicates that an entity has the ability, skill, or qualification to perform a task or fulfill a role effectively.
-
E.
competenceArea
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.