Triple
T37842035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipeline Masters |
E943504
|
entity |
| Predicate | primaryJudgingCriteria |
P7594
|
FINISHED |
| Object | tube riding |
—
|
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: tube riding | Statement: [Pipeline Masters, primaryJudgingCriteria, tube riding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryJudgingCriteria Context triple: [Pipeline Masters, primaryJudgingCriteria, tube riding]
-
A.
primaryCriterion
chosen
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
-
B.
ratingCriteria
Indicates the standards or factors used to evaluate and assign a rating to something.
-
C.
centralCriterion
Indicates that something serves as the primary or most important standard or basis for making a judgment, decision, or classification.
-
D.
judgedBy
Indicates that one entity evaluates, assesses, or forms an opinion about another entity, often in an official or critical capacity.
-
E.
judgeQualification
Indicates that one entity evaluates and determines whether another entity meets certain standards, criteria, or requirements.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.