Triple
T17286453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 420 dinghy |
E419666
|
entity |
| Predicate | isYouthPathwayClassFor |
P31810
|
FINISHED |
| Object | 470 dinghy |
—
|
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: 470 dinghy | Statement: [420 dinghy, isYouthPathwayClassFor, 470 dinghy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isYouthPathwayClassFor Context triple: [420 dinghy, isYouthPathwayClassFor, 470 dinghy]
-
A.
hasPlayerPathway
Indicates that there is a defined developmental or progression route available for a player within a given context or system.
-
B.
isInEducationalSystemOf
Indicates that one entity belongs to, is administered by, or operates within the educational system governed by another entity.
-
C.
isYouthEquivalentOf
chosen
Indicates that one entity is the youth or junior counterpart of another, typically representing a younger or age-specific version of the same role, group, or category.
-
D.
hasGradeSpan
Indicates the range of grade levels or educational stages that an entity (such as a school or program) covers or serves.
-
E.
hasStudentCategory
Indicates that an entity is classified under a specific category or type of student.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4378024988190aac6aec006f8f7a1 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.