Triple
T29794923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gTLDs |
E756517
|
entity |
| Predicate | examplePolicyRestriction |
P125239
|
FINISHED |
| Object | eligibility requirements for .edu |
—
|
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: eligibility requirements for .edu | Statement: [gTLDs, examplePolicyRestriction, eligibility requirements for .edu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examplePolicyRestriction Context triple: [gTLDs, examplePolicyRestriction, eligibility requirements for .edu]
-
A.
policyRestriction
chosen
Indicates that an entity is subject to a limiting rule, condition, or constraint imposed by a policy.
-
B.
locationPolicy
Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
-
C.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
D.
publicPolicyRole
Indicates that an entity holds or fulfills a role related to the creation, implementation, or influence of public policy.
-
E.
eraPolicy
Indicates that a specific policy was in effect during a particular historical or temporal era.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 5:14 p.m.