Triple
T28171272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armored Car Robbery |
E715463
|
entity |
| Predicate | hasHeistSequence |
P178787
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Armored Car Robbery, hasHeistSequence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeistSequence Context triple: [Armored Car Robbery, hasHeistSequence, true]
-
A.
heistOutcome
Indicates the result or consequence of a heist, such as its success, failure, or specific aftermath.
-
B.
survivesHeist
Indicates that an entity successfully endures and remains unharmed or intact through the course of a heist.
-
C.
hasChaseSequence
Indicates that one entity pursues another in a continuous or dynamic chase sequence.
-
D.
hasRitualSequence
Indicates that one ritual is ordered to occur before or after another within a defined ceremonial sequence.
-
E.
hasThiefCharacter
Indicates that an entity includes or features a character whose role or identity is that of a thief.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 27, 2026, 10:13 p.m.