Triple
T34579280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perl 5 porters |
E887843
|
entity |
| Predicate | emailListName |
P179334
|
FINISHED |
| Object | perl5-porters |
—
|
NE NERFINISHED |
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: perl5-porters | Statement: [Perl 5 porters, emailListName, perl5-porters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emailListName Context triple: [Perl 5 porters, emailListName, perl5-porters]
-
A.
mailRoute
Indicates a route or path along which mail or postal items are transported between locations.
-
B.
mailSystemType
Indicates the type or category of mail system associated with or used by an entity.
-
C.
emailSupport
Indicates that one entity provides assistance or help to another via email communication.
-
D.
mailboxModel
Indicates a relationship where an entity functions as or is associated with a specific mailbox configuration or structural model.
-
E.
includedEmailClient
Indicates that one entity has an email client contained, bundled, or provided as part of it.
- F. None of above. chosen
Provenance (4 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720c26c208190b0625097eb598f1d |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:03 a.m.