Triple
T9899676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOC 1 |
E182251
|
entity |
| Predicate | reportPeriodTypicalLength |
P84192
|
FINISHED |
| Object | 6 to 12 months for Type II reports |
—
|
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: 6 to 12 months for Type II reports | Statement: [SOC 1, reportPeriodTypicalLength, 6 to 12 months for Type II reports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportPeriodTypicalLength Context triple: [SOC 1, reportPeriodTypicalLength, 6 to 12 months for Type II reports]
-
A.
typicalPeriod
chosen
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
paymentPeriodLength
Indicates the duration or length of time that each payment period covers in a recurring payment or billing schedule.
-
D.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
-
E.
aboutPeriod
Indicates that something (such as a work, record, or statement) concerns or pertains to a specific 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4adc03481909e0f657db01e5bab |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.