Triple
T14602775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oghul-Khoimish |
E342744
|
entity |
| Predicate | sourceCharacterization |
P115013
|
FINISHED |
| Object | possibly apocryphal |
—
|
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: possibly apocryphal | Statement: [Oghul-Khoimish, sourceCharacterization, possibly apocryphal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceCharacterization Context triple: [Oghul-Khoimish, sourceCharacterization, possibly apocryphal]
-
A.
scopeCharacterization
Indicates how the extent, boundaries, or coverage of something is defined, described, or qualified in relation to another entity or context.
-
B.
resultCharacterization
Indicates how the outcome of an event, process, or action is qualitatively described or characterized.
-
C.
initialCharacterization
Indicates the first or earliest formal description, assessment, or classification made about an entity or situation.
-
D.
ruleCharacterization
Indicates that one rule is described, defined, or characterized in terms of another rule or set of rules.
-
E.
findingCharacterization
Indicates that a finding is being described or classified in terms of its nature, features, or diagnostic significance.
- F. None of above. chosen
Provenance (4 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43a1bb48190bf520cb961f15b5e |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:25 a.m.