Triple
T306655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMAP |
E6317
|
entity |
| Predicate | differenceFromPOP3 |
P9932
|
FINISHED |
| Object | supports multiple folders on server |
—
|
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: supports multiple folders on server | Statement: [IMAP, differenceFromPOP3, supports multiple folders on server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceFromPOP3 Context triple: [IMAP, differenceFromPOP3, supports multiple folders on server]
-
A.
pointDifference
Indicates the numerical difference in points or scores between two compared entities.
-
B.
formsDeltaWith
Indicates that one entity combines or interacts with another to produce a change or difference (a “delta”) between states, values, or conditions.
-
C.
mailboxModel
chosen
Indicates a relationship where an entity functions as or is associated with a specific mailbox configuration or structural model.
-
D.
hasGrammarDifferenceFrom
Indicates that two linguistic items differ from each other in their grammatical form, structure, or rules of usage.
-
E.
hasDelta
Indicates that there is a change, difference, or deviation between two related states, values, or versions of something.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea313be88190b4441f3ea41a99e2 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.