Triple
T9606931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States House Select Committee on Benghazi |
E231994
|
entity |
| Predicate | investigatedDateRange |
P78870
|
FINISHED |
| Object | 2012-09-11/2012-09-12 |
—
|
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: 2012-09-11/2012-09-12 | Statement: [United States House Select Committee on Benghazi, investigatedDateRange, 2012-09-11/2012-09-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigatedDateRange Context triple: [United States House Select Committee on Benghazi, investigatedDateRange, 2012-09-11/2012-09-12]
-
A.
occurredBetween
chosen
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
B.
createdBetween
Indicates that something was created within a specified start and end time or date range.
-
C.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
D.
timePeriodAnalyzed
Indicates that a specified time period is the focus or scope of an analysis or evaluation.
-
E.
concludedBetween
Indicates that an agreement, arrangement, or formal relationship has been finalized between two or more parties.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a62372881908bf21be91e7285fb |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.