Triple
T3460913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meteor |
E73020
|
entity |
| Predicate | fuzing |
P27067
|
FINISHED |
| Object | proximity fuze |
—
|
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: proximity fuze | Statement: [Meteor, fuzing, proximity fuze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuzing Context triple: [Meteor, fuzing, proximity fuze]
-
A.
warheadFuzing
chosen
Indicates the method or mechanism by which a warhead is triggered or detonated in relation to its target or flight conditions.
-
B.
fuseType
Indicates the specific kind or category of fuse associated with or used in relation to an entity.
-
C.
fires
Indicates that an agent initiates the discharge or ignition of something, such as a weapon, engine, or explosive device, causing it to operate or go off.
-
D.
juz
Indicates a judgment or evaluation made about one entity in relation to another.
-
E.
bodyFusedWith
Indicates that two or more bodies or physical structures are joined together into a single, continuous unit.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae745e081909007cd3a664c57f3 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.