Triple
T28541064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Around the Horn |
E722290
|
entity |
| Predicate | hasModeratorRole |
P161
|
FINISHED |
| Object | host awards and deducts points |
—
|
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: host awards and deducts points | Statement: [Around the Horn, hasModeratorRole, host awards and deducts points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModeratorRole Context triple: [Around the Horn, hasModeratorRole, host awards and deducts points]
-
A.
hasAdministratorRole
Indicates that an entity holds administrative authority or permissions over another entity or system.
-
B.
usesModerator
Indicates that an entity employs or relies on a moderator to oversee, regulate, or manage its interactions or processes.
-
C.
moderatorType
Indicates the role or category of moderation associated with an entity within a system or context.
-
D.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
E.
hasAdultStaffRole
Indicates that an entity holds a staff position or role designated specifically for adults.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 28, 2026, 3:35 a.m.