Triple
T27735280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Net.Mail.MailMessage |
E697513
|
entity |
| Predicate | hasCollectionPropertyType |
P338
|
FINISHED |
| Object | To: MailAddressCollection |
—
|
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: To: MailAddressCollection | Statement: [System.Net.Mail.MailMessage, hasCollectionPropertyType, To: MailAddressCollection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectionPropertyType Context triple: [System.Net.Mail.MailMessage, hasCollectionPropertyType, To: MailAddressCollection]
-
A.
hasCollectionType
chosen
Indicates that an entity is associated with or organized under a specific type or category of collection.
-
B.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
-
C.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
D.
hasCollectionMethod
Indicates the method or procedure by which something is gathered, obtained, or collected.
-
E.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: April 27, 2026, 3:12 p.m.