Triple
T197902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldcon |
E4037
|
entity |
| Predicate | membershipGrants |
P168
|
FINISHED |
| Object | right to vote for Hugo Awards |
—
|
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: right to vote for Hugo Awards | Statement: [Worldcon, membershipGrants, right to vote for Hugo Awards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipGrants Context triple: [Worldcon, membershipGrants, right to vote for Hugo Awards]
-
A.
memberCategory
Indicates that an entity belongs to or is classified under a specific category or group.
-
B.
membershipSpread
Indicates how widely membership in a group, organization, or category is distributed across different entities or locations.
-
C.
membershipPeak
Indicates the time or period at which an entity’s membership in a group or organization reaches its highest level.
-
D.
membershipDecidedBy
Indicates that the determination of whether an entity is granted membership in a group, organization, or set is made by another specified entity or process.
-
E.
grantedTo
chosen
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25be47ea881909c296b30a0d47a65 |
completed | Feb. 28, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69a25b47481c8190add47c641c977bb9 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.