Triple
T28397828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Νοῦς |
E719326
|
entity |
| Predicate | hasModeOfKnowing |
P183109
|
FINISHED |
| Object | immediate intellectual intuition |
—
|
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: immediate intellectual intuition | Statement: [Νοῦς, hasModeOfKnowing, immediate intellectual intuition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModeOfKnowing Context triple: [Νοῦς, hasModeOfKnowing, immediate intellectual intuition]
-
A.
hasModeOfRevelation
Indicates the manner or channel through which something is revealed, communicated, or made known.
-
B.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
C.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
D.
haveKnowledgeSystem
Indicates that an entity possesses or maintains a structured system for organizing, storing, and accessing knowledge.
-
E.
knownToBe
Indicates that one entity is recognized or acknowledged as being a certain way, having a certain property, or fitting a particular description by others.
- F. None of above. chosen
Provenance (4 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f798387ea481909f51303f53a22e52 |
completed | May 3, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79798663481908d6bc48dd6a94ca6 |
completed | May 3, 2026, 6:44 p.m. |
Created at: April 28, 2026, 1:18 a.m.