Triple
T32518485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN Governmental Advisory Committee |
E831119
|
entity |
| Predicate | adviceOn |
P96535
|
FINISHED |
| Object | ICANN’s role in the coordination of the DNS |
—
|
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: ICANN’s role in the coordination of the DNS | Statement: [ICANN Governmental Advisory Committee, adviceOn, ICANN’s role in the coordination of the DNS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adviceOn Context triple: [ICANN Governmental Advisory Committee, adviceOn, ICANN’s role in the coordination of the DNS]
-
A.
providesAdviceOn
chosen
Indicates that one entity gives guidance, recommendations, or expert counsel to another entity regarding a particular subject or matter.
-
B.
topicOfAdvice
Indicates that one entity is the subject or focus about which advice is being given by another entity.
-
C.
advises
Indicates that one entity provides guidance, recommendations, or counsel to another entity.
-
D.
adviceStyle
Indicates how advice is typically given or communicated in a particular context or relationship.
-
E.
advisedWith
Indicates that one entity provided advice, guidance, or consultation to another 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1 a.m.