Triple
T4579104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 global surveillance disclosures |
E101809
|
entity |
| Predicate | dataTypeExposed |
P4241
|
FINISHED |
| Object | classified NSA documents |
—
|
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: classified NSA documents | Statement: [2013 global surveillance disclosures, dataTypeExposed, classified NSA documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTypeExposed Context triple: [2013 global surveillance disclosures, dataTypeExposed, classified NSA documents]
-
A.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
B.
dataTypeCollected
chosen
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
C.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
D.
attributeType
Indicates that one entity specifies the kind or category of attribute that characterizes another entity.
-
E.
exposureType
Indicates the specific manner or context in which one entity is exposed to another entity, condition, or influence.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd58e3e028819083c4662deb9f3c03 |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.