Triple
T12266541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrow missile system |
E292360
|
entity |
| Predicate | layerRole |
P93630
|
FINISHED |
| Object | upper-tier missile defense |
—
|
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: upper-tier missile defense | Statement: [Arrow missile system, layerRole, upper-tier missile defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layerRole Context triple: [Arrow missile system, layerRole, upper-tier missile defense]
-
A.
libraryRole
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
-
B.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
C.
stratificationRole
chosen
Indicates the role or function an entity plays within a hierarchical or layered structure used to organize or classify elements.
-
D.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
E.
LeafRole
Indicates that an entity functions as a terminal or lowest-level role in a hierarchical structure, with no subordinate roles beneath it.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.