Triple
T31223401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Cyber Force |
E796073
|
entity |
| Predicate | publiclyAcknowledged |
P69765
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [National Cyber Force, publiclyAcknowledged, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyAcknowledged Context triple: [National Cyber Force, publiclyAcknowledged, true]
-
A.
publiclyAnnouncedBy
Indicates that an action, decision, or piece of information was formally communicated to the public by a specified agent or entity.
-
B.
wasRecognizedAs
chosen
Indicates that an entity was formally identified, acknowledged, or designated as having a particular role, status, or quality.
-
C.
acknowledgedIn
Indicates that one entity formally recognizes, credits, or expresses appreciation for another entity within a specified work, context, or communication.
-
D.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
E.
becamePublic
Indicates that an entity transitioned from private or restricted status to being publicly accessible or publicly traded.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 29, 2026, 9:10 p.m.