Triple
T23594994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Buzzer |
E582587
|
entity |
| Predicate | ruleConstraint |
P12029
|
FINISHED |
| Object | each judge usually has limited number of uses per season |
—
|
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: each judge usually has limited number of uses per season | Statement: [Golden Buzzer, ruleConstraint, each judge usually has limited number of uses per season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleConstraint Context triple: [Golden Buzzer, ruleConstraint, each judge usually has limited number of uses per season]
-
A.
constraintLanguage
Indicates that a specific formal language or syntax is used to express or define a constraint.
-
B.
ruleNumber
Indicates that an entity is associated with a specific rule identified by its number within a set of rules.
-
C.
supportsConstraint
Indicates that one entity upholds, enforces, or is compatible with a specified constraint or set of constraints in relation to another entity.
-
D.
constrainedBy
chosen
Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
-
E.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08e9aa4819091099dfc2074b22d |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.