Triple
T32519027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN community |
E831132
|
entity |
| Predicate | hasAdvisoryCommittee |
P1396
|
FINISHED |
| Object | Governmental Advisory Committee |
—
|
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: Governmental Advisory Committee | Statement: [ICANN community, hasAdvisoryCommittee, Governmental Advisory Committee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdvisoryCommittee Context triple: [ICANN community, hasAdvisoryCommittee, Governmental Advisory Committee]
-
A.
hasCommittee
chosen
Indicates that an entity is associated with or overseen by a specific committee.
-
B.
hasCommitteeMembers
Indicates that a committee is composed of, or includes, specific individuals as its members.
-
C.
hasSubjectCommittees
Indicates that an entity is associated with one or more committees responsible for overseeing or managing its academic subjects or courses.
-
D.
hasTechnicalCommittee
Indicates that an entity is associated with or overseen by a specific technical committee.
-
E.
hasCommitteeFunction
Indicates that a committee is assigned or performs a specific function, role, or responsibility.
- 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_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1 a.m.