Triple
T8203139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intellect (Plotinus) |
E191625
|
entity |
| Predicate | modeOfExistence |
P50872
|
FINISHED |
| Object | timeless |
—
|
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: timeless | Statement: [Intellect (Plotinus), modeOfExistence, timeless]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfExistence Context triple: [Intellect (Plotinus), modeOfExistence, timeless]
-
A.
hasFormOfLife
Indicates that one entity possesses, exhibits, or is associated with a particular form or type of life.
-
B.
modelOfLife
Indicates that one entity serves as a conceptual or representative model describing the life, lifecycle, or living processes of another entity.
-
C.
proposesExistenceOf
Indicates that one entity puts forward or suggests that another entity should exist or be brought into existence.
-
D.
modalityOf
chosen
Indicates that one element specifies the manner, mood, or mode in which the action, event, or state expressed by another element is realized or presented.
-
E.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df9cac08190a890ded4c7fbd393 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.