Triple
T604568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Agency |
E11566
|
entity |
| Predicate | operatesInDomain |
P794
|
FINISHED |
| Object | signals intelligence |
—
|
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: signals intelligence | Statement: [National Security Agency, operatesInDomain, signals intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInDomain Context triple: [National Security Agency, operatesInDomain, signals intelligence]
-
A.
operatesWithin
chosen
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
B.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
C.
usedInDomain
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
D.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
E.
operatedInRegion
Indicates that an entity conducted operations or activities within a specified geographic region.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49e574444819087999404f3e3ffd9 |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49cf701e08190966d06b9ff4b582b |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.