Triple
T34111845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ik Oankar |
E874857
|
entity |
| Predicate | OankarMeaning |
P116873
|
FINISHED |
| Object | Creator |
—
|
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: Creator | Statement: [Ik Oankar, OankarMeaning, Creator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OankarMeaning Context triple: [Ik Oankar, OankarMeaning, Creator]
-
A.
oniMeaning
Indicates that one entity expresses or conveys the meaning or sense of another entity (such as a word, phrase, or symbol).
-
B.
orientationOfDeity
Indicates the directional or positional alignment associated with a deity in relation to a reference point or context.
-
C.
roleOfReferencedDeity
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
D.
ARMeaning
Indicates that an entity’s meaning, interpretation, or semantic content is being specified or defined in relation to another entity or context.
-
E.
spiritualMeaning
chosen
Indicates that one entity represents or conveys a symbolic, religious, or transcendent significance in relation to another.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb544848190aaeb8f766a95aaff |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.