Triple
T526417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Letter |
E10927
|
entity |
| Predicate | timePeriodOfExpandedUse |
P4017
|
FINISHED |
| Object | post-September 11, 2001 |
—
|
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: post-September 11, 2001 | Statement: [National Security Letter, timePeriodOfExpandedUse, post-September 11, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfExpandedUse Context triple: [National Security Letter, timePeriodOfExpandedUse, post-September 11, 2001]
-
A.
periodOfMajorUse
chosen
Indicates the time span during which something was primarily or most intensively used.
-
B.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
E.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d0d22081908aad915482d39e74 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0198ecc8190883849e5a8245963 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.