Triple
T21802498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Complete Sequence Number PDU |
E538270
|
entity |
| Predicate | sentWhen |
P145697
|
FINISHED |
| Object | periodic intervals |
—
|
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: periodic intervals | Statement: [Complete Sequence Number PDU, sentWhen, periodic intervals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentWhen Context triple: [Complete Sequence Number PDU, sentWhen, periodic intervals]
-
A.
sentAfter
Indicates that one message or item was sent at a later time than another specified message or item.
-
B.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
C.
dateSent
Indicates the specific date on which something (such as a message, document, or item) was sent from one party to another.
-
D.
sentDocumentTo
Indicates that one entity transmitted or delivered a document to another entity.
-
E.
sentOnMissionBy
Indicates that one entity was assigned or dispatched on a mission by another entity.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0780062688190a6c3a2a0364f0f77 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6c3a2898881909748935cf92f898c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 6:53 p.m.