Triple
T338843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STARTTLS |
E6787
|
entity |
| Predicate | pop3CommandKeyword |
P6857
|
FINISHED |
| Object | STLS |
—
|
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: STLS | Statement: [STARTTLS, pop3CommandKeyword, STLS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pop3CommandKeyword Context triple: [STARTTLS, pop3CommandKeyword, STLS]
-
A.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
B.
mailboxModel
Indicates a relationship where an entity functions as or is associated with a specific mailbox configuration or structural model.
-
C.
postNominalLetters
Indicates that a person is associated with specific letters placed after their name to denote qualifications, honors, or professional affiliations.
-
D.
commandType
chosen
Indicates the specific kind or category of command being issued or executed in the relationship.
-
E.
coreCommand
Indicates that one entity serves as the primary or central command or control authority over another entity or process.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae3a27c81909fc7deb600125fb1 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.