Triple
T8791453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNSO Council |
E209174
|
entity |
| Predicate | governsPolicyScope |
P5037
|
FINISHED |
| Object | gTLD registration policies |
—
|
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: gTLD registration policies | Statement: [GNSO Council, governsPolicyScope, gTLD registration policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsPolicyScope Context triple: [GNSO Council, governsPolicyScope, gTLD registration policies]
-
A.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
B.
containsPolicyOn
Indicates that one entity includes, references, or incorporates a specific policy within it.
-
C.
coversPolicyArea
chosen
Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
-
D.
declaredPolicy
Indicates that an entity has formally stated or announced a specific policy or course of action.
-
E.
organizationalScope
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f8e6e4881909155c40c52bc082c |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:43 p.m.