Triple
T8490081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board Compensation Committee |
E200944
|
entity |
| Predicate | formedForPurpose |
P39773
|
FINISHED |
| Object | oversight of executive and Board compensation at ICANN |
—
|
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: oversight of executive and Board compensation at ICANN | Statement: [Board Compensation Committee, formedForPurpose, oversight of executive and Board compensation at ICANN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedForPurpose Context triple: [Board Compensation Committee, formedForPurpose, oversight of executive and Board compensation at ICANN]
-
A.
usedForAdministrativePurposes
Indicates that something is employed in managing, organizing, or overseeing official, institutional, or organizational activities and records.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
formedTo
chosen
Indicates that one entity was created, established, or organized for the purpose of serving, supporting, or enabling another entity or activity.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5596f1c8190aead21a245f21c07 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.