Triple
T29662804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN community wiki |
E750454
|
entity |
| Predicate | usesCollaborationModel |
P1854
|
FINISHED |
| Object | multistakeholder model |
—
|
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: multistakeholder model | Statement: [ICANN community wiki, usesCollaborationModel, multistakeholder model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCollaborationModel Context triple: [ICANN community wiki, usesCollaborationModel, multistakeholder model]
-
A.
usesCollaboration
Indicates that one entity employs or relies on collaborative methods, tools, or partnerships with another entity to achieve a shared goal or perform an activity.
-
B.
collaborationModel
chosen
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
C.
containsCollaboration
Indicates that one entity includes or involves a collaborative relationship or joint activity with another entity.
-
D.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
E.
isCollaborative
Indicates that two or more entities work together jointly toward a shared goal or outcome.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 6:59 p.m.