Triple
T30388378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KCrash |
E773007
|
entity |
| Predicate | canInvoke |
P59606
|
FINISHED |
| Object | external crash reporter |
—
|
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: external crash reporter | Statement: [KCrash, canInvoke, external crash reporter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canInvoke Context triple: [KCrash, canInvoke, external crash reporter]
-
A.
canBeInvokedBy
chosen
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
B.
canConvoke
Indicates that one entity has the authority or ability to formally call another entity or group together for a meeting or assembly.
-
C.
canPerform
Indicates that one entity has the ability, permission, or capacity to carry out a specific action or function on or with another entity.
-
D.
canBeCalled
Indicates that one entity is able or permitted to be addressed, referred to, or named by another entity in a particular way.
-
E.
canBeCalledTo
Indicates that one entity is able or permitted to initiate a call or summon another entity.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685991b0c8190bc7ac8af9c65a010 |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:01 p.m.