Triple
T29227987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Underground bombing |
E740985
|
entity |
| Predicate | targetsOrganization |
P67775
|
FINISHED |
| Object | MI6 |
—
|
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: MI6 | Statement: [London Underground bombing, targetsOrganization, MI6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsOrganization Context triple: [London Underground bombing, targetsOrganization, MI6]
-
A.
targetOrganization
Indicates that one entity is the organization that is the focus, recipient, or primary subject of another entity’s action, service, or relationship.
-
B.
targetOrganizations
chosen
Indicates the organizations that are the intended recipients or focus of an action, initiative, or influence.
-
C.
controlledOrganization
Indicates that one entity has the authority to direct, manage, or significantly influence the operations and decisions of another organization.
-
D.
endedOrganization
Indicates that an organization has ceased to exist or operate, marking the termination of its existence or activities.
-
E.
centralOrganizationFor
Indicates that one organization serves as the primary or coordinating authority for another organization or group of entities.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 28, 2026, 12:17 p.m.