Triple
T26386995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryder rental truck |
E663307
|
entity |
| Predicate | loadedWith |
P160482
|
FINISHED |
| Object | explosives |
—
|
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: explosives | Statement: [Ryder rental truck, loadedWith, explosives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadedWith Context triple: [Ryder rental truck, loadedWith, explosives]
-
A.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
B.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
-
C.
acquiredWith
Indicates that one entity was obtained, purchased, or gained together with or by means of another entity.
-
D.
importedWith
Indicates that one entity was brought into a system, context, or location together with or as part of another entity during an import process.
-
E.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610bc2b288190ae10e6c27e5df786 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:23 p.m.