Triple
T9694785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bojinka plot |
E234619
|
entity |
| Predicate | evidenceRecovered |
P70490
|
FINISHED |
| Object | laptop computer with plot details |
—
|
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: laptop computer with plot details | Statement: [Bojinka plot, evidenceRecovered, laptop computer with plot details]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evidenceRecovered Context triple: [Bojinka plot, evidenceRecovered, laptop computer with plot details]
-
A.
hasMaterialEvidence
chosen
Indicates that there exists tangible, physical evidence supporting or associated with a particular entity, event, or claim.
-
B.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
C.
evidenceSeizedAt
Indicates that evidence was taken or confiscated at a specific location or during a particular event.
-
D.
recoveredIn
Indicates that something lost, damaged, or impaired has been restored or regained within a particular context, process, or location.
-
E.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d348868819083aec7a5da8c455b |
completed | April 1, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.