Triple
T37994941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extended Simple Mail Transfer Protocol |
E947921
|
entity |
| Predicate | commandIntroduced |
P195798
|
FINISHED |
| Object | EHLO |
—
|
NE NERFINISHED |
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: EHLO | Statement: [Extended Simple Mail Transfer Protocol, commandIntroduced, EHLO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandIntroduced Context triple: [Extended Simple Mail Transfer Protocol, commandIntroduced, EHLO]
-
A.
classIntroduced
Indicates that a particular class (e.g., in a programming language or system) has been newly defined or made available within a given context or scope.
-
B.
serviceIntroduced
Indicates that a particular service has been launched, made available, or brought into operation at a certain time or context.
-
C.
messageIntroducedWith
Indicates that one message is presented or initiated by means of another message or introductory content.
-
D.
engineIntroduced
Indicates that a particular engine was first introduced or brought into use at a specific time or in a specific context.
-
E.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69fde5d677b88190bc904e6df8617c18 |
completed | May 8, 2026, 1:32 p.m. |
Created at: May 3, 2026, 4:20 p.m.