Triple
T37462626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalimos, Primal Lord |
E930955
|
entity |
| Predicate | invocationCount |
P19112
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Kalimos, Primal Lord, invocationCount, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invocationCount Context triple: [Kalimos, Primal Lord, invocationCount, 4]
-
A.
invocationOf
Indicates that one entity is the act, event, or instance of calling upon, summoning, or appealing to another entity (such as a function, service, or authority) to perform its role or be brought into effect.
-
B.
invocationFlag
Indicates that an entity has been marked or configured to be invoked, often controlling whether a particular action, method, or process should be executed.
-
C.
invocationType
Indicates the manner or mode in which an action, function, or process is called, triggered, or executed.
-
D.
numberOfExecutions
chosen
Indicates the count of times a particular action, process, or event has been carried out.
-
E.
invocationInterface
Indicates that one entity serves as the interface or entry point through which another entity is invoked, called, or executed.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.