Triple
T3801462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York County grand jury |
E91696
|
entity |
| Predicate | proceedingsAre |
P51838
|
FINISHED |
| Object | secret |
—
|
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: secret | Statement: [New York County grand jury, proceedingsAre, secret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceedingsAre Context triple: [New York County grand jury, proceedingsAre, secret]
-
A.
coversProceedings
Indicates that one entity reports on, documents, or provides coverage of a set of proceedings or events involving another entity.
-
B.
proceedingsIndexedIn
Indicates that a set of proceedings is included and recorded in a specific indexing service or database.
-
C.
academicConference
Indicates a relationship where an event functions as an academic conference, typically involving scholarly presentations, discussions, and exchanges among researchers or professionals.
-
D.
parallelConference
Indicates that two or more conferences occur at the same time or overlap in schedule, running in parallel to each other.
-
E.
typeOfProceedings
Indicates the specific category or kind of legal or formal process under which an action or case is being conducted.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:15 p.m.