Triple
T23281332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citizens' Commission to Investigate the FBI |
E588870
|
entity |
| Predicate | distributedDocumentsTo |
P151658
|
FINISHED |
| Object | journalists |
—
|
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: journalists | Statement: [Citizens' Commission to Investigate the FBI, distributedDocumentsTo, journalists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributedDocumentsTo Context triple: [Citizens' Commission to Investigate the FBI, distributedDocumentsTo, journalists]
-
A.
documentsNow
Indicates that an entity is currently documenting, recording, or writing about another entity at the present time.
-
B.
documentsCommunity
Indicates that an entity records, describes, or provides information about a particular community.
-
C.
documentList
Indicates a relationship where one entity serves as a list or collection of documents associated with another entity.
-
D.
documentsResponseTo
Indicates that one entity records, describes, or formally captures the reply, outcome, or reaction to another entity.
-
E.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19643b8908190a2c29552b272dc61 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:57 p.m.