Triple
T38593778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonic Arrow |
E932514
|
entity |
| Predicate | triggersFrom |
P191464
|
FINISHED |
| Object | impact location |
—
|
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: impact location | Statement: [Sonic Arrow, triggersFrom, impact location]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggersFrom Context triple: [Sonic Arrow, triggersFrom, impact location]
-
A.
triggeredFrom
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
-
B.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
-
C.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
D.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
E.
typicalTrigger
Indicates that one entity commonly or characteristically causes, initiates, or brings about the occurrence of another entity or event.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.