Triple
T935170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notarikon |
E20178
|
entity |
| Predicate | interpretiveLevel |
P11425
|
FINISHED |
| Object | sod |
—
|
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: sod | Statement: [Notarikon, interpretiveLevel, sod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretiveLevel Context triple: [Notarikon, interpretiveLevel, sod]
-
A.
interpretiveStatus
Indicates the evaluative or explanatory stance assigned to something, such as how it is understood, classified, or interpreted within a given context.
-
B.
logicalLevel
chosen
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
-
C.
interpretedInCase
Indicates that something is understood, analyzed, or given meaning within the context of a particular case or specific situational scenario.
-
D.
intelligenceLevel
Indicates the degree or measure of cognitive ability or intelligence attributed to an entity.
-
E.
interpretedAs
Indicates that something is understood, perceived, or taken to mean something else, often based on context or subjective judgment.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b363ea5c819098ec1d87f785bad4 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.