Triple
T9648231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RT-2 ICBM |
E233262
|
entity |
| Predicate | roleInArsenal |
P74123
|
FINISHED |
| Object | part of Soviet strategic nuclear forces |
—
|
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: part of Soviet strategic nuclear forces | Statement: [RT-2 ICBM, roleInArsenal, part of Soviet strategic nuclear forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInArsenal Context triple: [RT-2 ICBM, roleInArsenal, part of Soviet strategic nuclear forces]
-
A.
arsenalRole
chosen
Indicates the functional role or position an entity holds within an arsenal or weapons-related context.
-
B.
roleInManchesterCity
Indicates that an entity holds or has held a specific role or position within Manchester City Football Club.
-
C.
roleInFootballHistory
Indicates the specific part or significance an entity has within the historical development, events, or legacy of football.
-
D.
postArsenalRole
Indicates the role or position an entity holds after their time or involvement with Arsenal has ended.
-
E.
trophyWonWithArsenal
Indicates that a trophy was won by a person or team while they were with Arsenal Football Club.
- 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bac55b48190ab2a8f9bb83c951e |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:13 p.m.