Triple
T32378500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Server-Sent Events |
E827349
|
entity |
| Predicate | messageFormatField |
P173996
|
FINISHED |
| Object | data |
—
|
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: data | Statement: [Server-Sent Events, messageFormatField, data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: messageFormatField Context triple: [Server-Sent Events, messageFormatField, data]
-
A.
segmentFormat
Indicates how a segment or portion of a larger whole is structured, arranged, or encoded in relation to that whole.
-
B.
dateFormat
Indicates the specific pattern or structure used to represent a date as a formatted string.
-
C.
formatPartOf
Indicates that one entity functions as a component or segment within the overall structure or composition of another entity.
-
D.
formatStrategy
Indicates the method or approach used to structure, arrange, or present information or content.
-
E.
valueFormatExample
Indicates an example of how a value should be formatted or represented.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c13307548190b3e209bff21ab524 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:51 a.m.