Triple
T36453993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mailman |
E898099
|
entity |
| Predicate | supportsArchiver |
P204879
|
FINISHED |
| Object | HyperKitty |
E2184349
|
NE 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: HyperKitty | Statement: [Mailman, supportsArchiver, HyperKitty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsArchiver Context triple: [Mailman, supportsArchiver, HyperKitty]
-
A.
supportedArchitect
Indicates that one entity provides architectural backing, endorsement, or assistance to another entity or architectural concept.
-
B.
supportsThinArchives
Indicates that one entity provides compatibility with or functionality for handling thin archives associated with another entity.
-
C.
supportsCompressedFiles
Indicates that one entity is capable of handling, reading, or working with files that are stored in a compressed format.
-
D.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
-
E.
supportsPackagingModel
Indicates that one entity provides compatibility with or functionality for a particular packaging model used by another entity.
- F. None of above. chosen
Provenance (5 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfcac9788190aeeb42062bd9b2dc |
completed | June 23, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.