Triple
T6063124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiree Wave Classic |
E135085
|
entity |
| Predicate | usesJudgingCriteria |
P36515
|
FINISHED |
| Object | wave selection |
—
|
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: wave selection | Statement: [Tiree Wave Classic, usesJudgingCriteria, wave selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesJudgingCriteria Context triple: [Tiree Wave Classic, usesJudgingCriteria, wave selection]
-
A.
judgedBy
Indicates that one entity evaluates, assesses, or forms an opinion about another entity, often in an official or critical capacity.
-
B.
judgedAs
Indicates that one entity evaluates or forms an opinion about another entity according to some criteria or standard.
-
C.
evaluationCriteriaInclude
chosen
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
D.
judgesMayBe
Indicates that certain individuals can serve in the role of judges under specified conditions or classifications.
-
E.
usedToCritique
Indicates that something is employed as a means to analyze, evaluate, or express disapproval of something else.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05722815081909ee47e8f94b87b3a |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.