Triple
T20635430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bomb burst maneuver |
E507062
|
entity |
| Predicate | isDesignedToBeViewedFrom |
P9494
|
FINISHED |
| Object | ground spectators |
—
|
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: ground spectators | Statement: [bomb burst maneuver, isDesignedToBeViewedFrom, ground spectators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDesignedToBeViewedFrom Context triple: [bomb burst maneuver, isDesignedToBeViewedFrom, ground spectators]
-
A.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
-
B.
hasViewingSide
Indicates that one entity serves as the side or surface of another entity that is intended to be viewed or observed.
-
C.
viewIs
Indicates that one entity is a visual representation or perspective of another entity.
-
D.
hasViewingAngles
Indicates that one entity possesses or is characterized by specific viewing angles relative to another entity or reference frame.
-
E.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0f5a88819090c1516f5543f3d4 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.