Triple
T8203138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intellect (Plotinus) |
E191625
|
entity |
| Predicate | isKnownBy |
P27854
|
FINISHED |
| Object | contemplative ascent of the soul |
—
|
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: contemplative ascent of the soul | Statement: [Intellect (Plotinus), isKnownBy, contemplative ascent of the soul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKnownBy Context triple: [Intellect (Plotinus), isKnownBy, contemplative ascent of the soul]
-
A.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
B.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
C.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
-
D.
isBestKnownFrom
Indicates that an entity is primarily or most famously recognized in connection with a particular source, context, or work.
-
E.
recognizedThrough
chosen
Indicates that something becomes known, identified, or acknowledged by means of a particular method, medium, or process.
- 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.