Triple
T13002333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C public mailing list infrastructure |
E322197
|
entity |
| Predicate | typicalListNamePattern |
P60600
|
FINISHED |
| Object | public-<topic>@w3.org |
—
|
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: public-<topic>@w3.org | Statement: [W3C public mailing list infrastructure, typicalListNamePattern, public-<topic>@w3.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalListNamePattern Context triple: [W3C public mailing list infrastructure, typicalListNamePattern, public-<topic>@w3.org]
-
A.
namePattern
chosen
Indicates that an entity’s name follows or matches a specified pattern or format.
-
B.
typicalNameLength
Indicates the usual or characteristic number of characters in the names of entities in a given context.
-
C.
onNameTypeLists
Indicates that something appears on one or more lists that are categorized or organized by name type.
-
D.
typicalFullName
Indicates that the object is the standard or commonly used full name associated with the subject.
-
E.
typicalCaseTypes
Indicates the kinds or categories of cases that are most commonly associated with or handled by a given 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9828748190b2ad9ea29180b7d3 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:47 p.m.