Triple
T2143789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hesychast tradition |
E47017
|
entity |
| Predicate | seeksExperienceOf |
P22183
|
FINISHED |
| Object | uncreated light |
—
|
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: uncreated light | Statement: [hesychast tradition, seeksExperienceOf, uncreated light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksExperienceOf Context triple: [hesychast tradition, seeksExperienceOf, uncreated light]
-
A.
typeOfExperience
chosen
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
B.
experienceType
Indicates the specific kind or category of experience associated with an entity or event.
-
C.
primaryExperience
Indicates that one entity is the main or most significant experience associated with another entity, as opposed to secondary or supporting experiences.
-
D.
targetOfficeSought
Indicates the specific public or organizational office or position that an individual is seeking or running for.
-
E.
appointmentRequirement
Indicates that a particular action, service, or interaction can only occur if an appointment has been scheduled or a specified appointment condition is met.
- 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.