Triple
T19177771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overmind |
E469482
|
entity |
| Predicate | knowledgeScope |
P134757
|
FINISHED |
| Object | near-omniscient |
—
|
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: near-omniscient | Statement: [Overmind, knowledgeScope, near-omniscient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knowledgeScope Context triple: [Overmind, knowledgeScope, near-omniscient]
-
A.
knowledgeType
Indicates the specific category or nature of knowledge associated with an entity or statement (e.g., factual, procedural, conceptual).
-
B.
knowledgeOutput
Indicates that an entity produces, expresses, or makes available knowledge, information, or learned content as an output.
-
C.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
D.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
E.
knowledgeSourceInUniverse
Indicates that a particular source or repository of knowledge exists or is valid within a specified universe or contextual domain.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f618f18c8190b98995fda4b6fea0 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:07 p.m.