Triple
T3577850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRISM |
E75729
|
entity |
| Predicate | agencyTypeOfOperator |
P49812
|
FINISHED |
| Object | signals intelligence agency |
—
|
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 agency | Statement: [PRISM, agencyTypeOfOperator, signals intelligence agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agencyTypeOfOperator Context triple: [PRISM, agencyTypeOfOperator, signals intelligence agency]
-
A.
aircraftOperator
Indicates that one entity operates, manages, or is responsible for the use of a particular aircraft.
-
B.
transportOperator
Indicates that an entity is responsible for operating or managing the transportation of people or goods between locations.
-
C.
belongsToAirportOperator
Indicates that an airport or related facility is owned, managed, or operated by a specific airport operating organization.
-
D.
wirelessOperator
Indicates that an entity operates, manages, or provides services for a wireless communication system or network for another entity.
-
E.
operatedByCompanyHeadquarteredIn
Indicates that an entity is operated by a company whose headquarters is located in a specified place.
- F. None of above. chosen
Provenance (4 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0dd3e048190a0c6666e13ead9cd |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:21 p.m.