Triple
T4021211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNIP |
E91282
|
entity |
| Predicate | timeWindow |
P38735
|
FINISHED |
| Object | three-year citation window |
—
|
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: three-year citation window | Statement: [SNIP, timeWindow, three-year citation window]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeWindow Context triple: [SNIP, timeWindow, three-year citation window]
-
A.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
C.
timeFrameSpecified
chosen
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
D.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
E.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefacb4c208190b8dd595a534850b2 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.