Triple
T4643245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 03 Chū-SAM |
E101703
|
entity |
| Predicate | deploymentRole |
P44182
|
FINISHED |
| Object | area air 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: area air defense | Statement: [Type 03 Chū-SAM, deploymentRole, area air defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentRole Context triple: [Type 03 Chū-SAM, deploymentRole, area air defense]
-
A.
configurationRole
chosen
Indicates the role or function an entity assumes within a particular configuration or setup.
-
B.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
-
C.
developmentRole
Indicates that an entity participates in the creation, design, or production of another entity in a specific developmental capacity or function.
-
D.
platformRole
Indicates the specific function, position, or level of responsibility an entity holds within a given platform or system.
-
E.
deploymentRequires
Indicates that performing a particular deployment is contingent upon the prior existence, completion, or availability of another specified resource, condition, or action.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a93047c8190990c94fd5a57c867 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:14 p.m.