Triple
T1866893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMTP AUTH |
E34941
|
entity |
| Predicate | usesCommand |
P22505
|
FINISHED |
| Object | AUTH |
—
|
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: AUTH | Statement: [SMTP AUTH, usesCommand, AUTH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommand Context triple: [SMTP AUTH, usesCommand, AUTH]
-
A.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
B.
supportsCommand
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
C.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
D.
containsCommand
chosen
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
E.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.