Triple
T18015296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mail (Flask-Mail) |
E430983
|
entity |
| Predicate | exampleImport |
P128018
|
FINISHED |
| Object | from flask_mail import Mail |
—
|
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: from flask_mail import Mail | Statement: [Mail (Flask-Mail), exampleImport, from flask_mail import Mail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleImport Context triple: [Mail (Flask-Mail), exampleImport, from flask_mail import Mail]
-
A.
moduleImport
chosen
Indicates that one module brings another module into its scope to use its definitions or functionality.
-
B.
importedWith
Indicates that one entity was brought into a system, context, or location together with or as part of another entity during an import process.
-
C.
imported
Indicates that something was brought into a country, system, or context from an external source.
-
D.
primaryImports
Indicates that one entity is the main or predominant source from which another entity imports goods, services, or resources.
-
E.
exampleType
Indicates that one entity serves as a representative or illustrative instance of the type or category defined by 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b522e84c8190a03f6445df9f5ac8 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.