Triple
T1081605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Controlled Unclassified Information program |
E23957
|
entity |
| Predicate | usesMarking |
P2130
|
FINISHED |
| Object | CUI banner markings |
—
|
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: CUI banner markings | Statement: [Controlled Unclassified Information program, usesMarking, CUI banner markings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMarking Context triple: [Controlled Unclassified Information program, usesMarking, CUI banner markings]
-
A.
hasCaseMarking
Indicates that a linguistic element (such as a noun or pronoun) bears a specific grammatical case marking that signals its syntactic or semantic role in a clause.
-
B.
mintMarkUsedOn
Indicates that a particular mint mark was applied to or appears on a specific coin or numismatic item.
-
C.
hasMarker
chosen
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
D.
usesIndicator
Indicates that one entity employs or relies on another entity as an indicator, signal, or metric for assessment, decision-making, or interpretation.
-
E.
markType
Indicates the specific category or kind of mark associated with or applied to an 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.