Triple
T27692357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarifications to the DNS Specification |
E698191
|
entity |
| Predicate | wg |
P162954
|
FINISHED |
| Object | DNSIND Working Group |
—
|
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: DNSIND Working Group | Statement: [Clarifications to the DNS Specification, wg, DNSIND Working Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wg Context triple: [Clarifications to the DNS Specification, wg, DNSIND Working Group]
-
A.
wand
Indicates that one entity uses or possesses a wand as an instrument or tool in relation to another entity or action.
-
B.
wing
Indicates that an entity has a wing or is equipped with wings as a physical feature or structural component.
-
C.
guna
Indicates that an entity uses, employs, or makes use of another entity as a means, tool, or resource to perform an action or achieve a purpose.
-
D.
wingOf
Indicates that something is a wing that forms a physical or functional part of another entity.
-
E.
wonGroup
Indicates that an entity achieved first place or overall victory within a specific group, pool, or division of a competition or tournament.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63578a9cc8190a1f75ca0afbca964 |
completed | May 2, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 2:52 p.m.