Triple
T17315581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiama Knights rugby league club |
E420413
|
entity |
| Predicate | primaryCode |
P126950
|
FINISHED |
| Object | rugby league |
—
|
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: rugby league | Statement: [Kiama Knights rugby league club, primaryCode, rugby league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCode Context triple: [Kiama Knights rugby league club, primaryCode, rugby league]
-
A.
primaryIdentification
Indicates that one identifier is the main or officially recognized identification for an entity among possibly multiple identifiers.
-
B.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
C.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
D.
primaryField
Indicates the main area of focus, discipline, or domain most centrally associated with an entity.
-
E.
primaryClass
Indicates that one entity is the main or principal classification category to which another entity belongs.
- F. None of above. chosen
Provenance (4 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399c6ad88190ba7fcf1d2d53171c |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.