Triple
T37003987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota high school music contests |
E915731
|
entity |
| Predicate | adjudicatorType |
P10518
|
FINISHED |
| Object | music educators |
—
|
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: music educators | Statement: [Minnesota high school music contests, adjudicatorType, music educators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjudicatorType Context triple: [Minnesota high school music contests, adjudicatorType, music educators]
-
A.
adjudicationType
Indicates the specific kind or category of formal judgment or decision rendered in a legal or administrative adjudication process.
-
B.
canAdjudicate
Indicates that an entity has the authority or capacity to formally judge, decide, or resolve a dispute, case, or issue involving another entity or matter.
-
C.
hasJudgeType
chosen
Indicates that an entity is associated with a specific category or type of judge.
-
D.
judgeAppointmentBy
Indicates that one entity is appointed to the role of judging or evaluating another entity by a specific authority or process.
-
E.
judge
Indicates that one entity evaluates, forms an opinion about, or makes a decision regarding another entity or situation.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.