Triple
T29756512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standoff |
E753042
|
entity |
| Predicate | unitDepicted |
P167847
|
FINISHED |
| Object | FBI Crisis Negotiation Unit |
—
|
NE NERFINISHED |
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: FBI Crisis Negotiation Unit | Statement: [Standoff, unitDepicted, FBI Crisis Negotiation Unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitDepicted Context triple: [Standoff, unitDepicted, FBI Crisis Negotiation Unit]
-
A.
imageDepictedIn
Indicates that a particular image is shown, represented, or included within another resource or context.
-
B.
isDepictedVia
Indicates that one entity is represented, illustrated, or shown by means of another entity, such as a specific medium, style, or method of depiction.
-
C.
componentRepresents
Indicates that one component stands in for, symbolizes, or models another entity or concept within a system or context.
-
D.
commonlyDepictedOn
Indicates that something is frequently shown or represented on the surface, medium, or context of another thing.
-
E.
depictsTool
Indicates that one entity visually represents or shows a tool in some form of depiction (e.g., an image, illustration, or artwork).
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673cbcbac819098e3b944b6fcfd1e |
completed | May 2, 2026, 9:59 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 28, 2026, 7:57 p.m.