Triple
T23488720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SVPNPA |
E570611
|
entity |
| Predicate | hasFiringRange |
P152572
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SVPNPA, hasFiringRange, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFiringRange Context triple: [SVPNPA, hasFiringRange, yes]
-
A.
hasCannon
Indicates that one entity is equipped with, contains, or features a cannon.
-
B.
shootingRange
Indicates that one entity serves as a location or facility where another entity engages in shooting activities, typically for practice or training.
-
C.
hasFireControlSystem
Indicates that an entity is equipped with or includes a fire control system used to detect, track, and direct weapons or suppression against targets.
-
D.
hasShootingPosition
Indicates that an entity has a designated location or spot from which shooting (e.g., firing a weapon or taking a shot) is performed.
-
E.
rateOfFire
Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dae8cc8190bf74d1bdb0fc6c60 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:04 p.m.