Triple
T31704281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAAMS |
E809137
|
entity |
| Predicate | coverageDomain |
P121917
|
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: [PAAMS, coverageDomain, area air defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverageDomain Context triple: [PAAMS, coverageDomain, area air defense]
-
A.
coverageBasis
Indicates the underlying principle, rule, or criteria on which a particular coverage or protection is determined or applied.
-
B.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
C.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
D.
coverageWindow
Indicates the time period or range during which coverage, protection, or applicability of something is in effect.
-
E.
affectedDomain
chosen
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 30, 2026, 11:13 p.m.