Triple
T6327260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-Code |
E141890
|
entity |
| Predicate | notAvailableTo |
P69175
|
FINISHED |
| Object | civilian users |
—
|
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: civilian users | Statement: [M-Code, notAvailableTo, civilian users]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAvailableTo Context triple: [M-Code, notAvailableTo, civilian users]
-
A.
notAvailableFor
chosen
Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
-
B.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
C.
availableFor
Indicates that one entity can be used, accessed, or allocated for the benefit, purpose, or use of another entity.
-
D.
notSoldIn
Indicates that a product or item is unavailable for purchase within a specified market, region, or sales channel.
-
E.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e9532081908277f10ec380a486 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.