Triple
T5223935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scholia on Proverbs |
E117937
|
entity |
| Predicate | usesInterpretiveMethod |
P21759
|
FINISHED |
| Object | allegorical exegesis |
—
|
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: allegorical exegesis | Statement: [Scholia on Proverbs, usesInterpretiveMethod, allegorical exegesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInterpretiveMethod Context triple: [Scholia on Proverbs, usesInterpretiveMethod, allegorical exegesis]
-
A.
interpretationMethod
chosen
Indicates the method, technique, or process used to interpret or derive meaning from something.
-
B.
isInterpretedBy
Indicates that something (such as data, a work, or a signal) is given meaning, understanding, or explanation by a particular agent or process.
-
C.
hasInterpretiveSigns
Indicates that interpretive or informational signs are present at or associated with the subject.
-
D.
containsInterpretationOf
Indicates that one entity includes or embodies an interpretation or understanding of another entity.
-
E.
hasInterpretiveElement
Indicates that something includes or is associated with an element involving interpretation, such as a subjective, analytical, or explanatory component.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7abd3ed48190bfd8d2f2ca399741 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.