Triple
T2751858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet-Drafts |
E61006
|
entity |
| Predicate | typicalExpirationPeriod |
P41643
|
FINISHED |
| Object | 6 months |
—
|
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 months | Statement: [Internet-Drafts, typicalExpirationPeriod, 6 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalExpirationPeriod Context triple: [Internet-Drafts, typicalExpirationPeriod, 6 months]
-
A.
removalPeriod
Indicates the time span during which something is taken away, deleted, or otherwise removed from availability or consideration.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
E.
expirationPolicy
Indicates the rules or conditions under which something becomes invalid, unusable, or no longer in effect after a certain time or event.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb6d08088190b489de15a120ba3f |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd91497ec8190927e91ad33549eda |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:56 p.m.