Triple
T31786915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasman Rugby Union |
E811356
|
entity |
| Predicate | governsAgeGrades |
P176683
|
FINISHED |
| Object | senior rugby |
—
|
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: senior rugby | Statement: [Tasman Rugby Union, governsAgeGrades, senior rugby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsAgeGrades Context triple: [Tasman Rugby Union, governsAgeGrades, senior rugby]
-
A.
governsAgeLevel
chosen
Indicates that one entity has authority or control over the age-related classification, restriction, or eligibility level applied to another entity.
-
B.
governsAgeEligibility
Indicates that one entity sets or controls the age-related criteria determining another entity’s eligibility for something.
-
C.
regulatesGradeLevels
Indicates a relationship where one entity sets or enforces rules or standards governing the grade levels of another entity.
-
D.
ageGradeSystem
Indicates the grading or classification system used to evaluate or categorize entities based on age.
-
E.
eligibilityGradeLevel
Indicates the grade level or range of grade levels for which an entity is considered eligible or appropriate.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: April 30, 2026, 11:38 p.m.