Triple
T32595190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y‑beam |
E833182
|
entity |
| Predicate | targetingRole |
P175301
|
FINISHED |
| Object | bomb release control |
—
|
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: bomb release control | Statement: [Y‑beam, targetingRole, bomb release control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetingRole Context triple: [Y‑beam, targetingRole, bomb release control]
-
A.
targetRole
chosen
Indicates the specific role or function that an entity is intended or designated to fulfill in a given context.
-
B.
targetQualification
Indicates that one entity specifies or defines the required qualification or eligibility criteria for another entity.
-
C.
symbolicRoleOfTarget
Indicates that the target entity serves as a symbolic representation or emblem for another entity or concept.
-
D.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
E.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 1, 2026, 1:05 a.m.