Triple
T696278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASRAAM |
E13900
|
entity |
| Predicate | fuseType |
P17582
|
FINISHED |
| Object | proximity fuse |
—
|
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 fuse | Statement: [ASRAAM, fuseType, proximity fuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuseType Context triple: [ASRAAM, fuseType, proximity fuse]
-
A.
fanType
Indicates the specific category or kind of fan associated with an entity, such as its design, purpose, or operating principle.
-
B.
furnaceType
Indicates the specific kind or category of furnace associated with an entity.
-
C.
typeOfFixing
Indicates the specific method or manner in which one entity is fastened, attached, or secured to another.
-
D.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
E.
forceType
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c5f51c8190acc4915099e4b384 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d23e0a08190b08be9d1eff2a1bb |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49df19c9481909cc9bc33ed7f011b |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.