Triple
T35176490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balmain Tigers |
E1015718
|
entity |
| Predicate | foundationCompetition |
P193580
|
FINISHED |
| Object | inaugural NSWRL premiership 1908 |
—
|
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: inaugural NSWRL premiership 1908 | Statement: [Balmain Tigers, foundationCompetition, inaugural NSWRL premiership 1908]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundationCompetition Context triple: [Balmain Tigers, foundationCompetition, inaugural NSWRL premiership 1908]
-
A.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competitionFoundedBy
Indicates that a particular competition was established or created by a specific person or organization.
-
C.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
D.
centralCompetition
Indicates a primary or core competitive relationship or contest that is central to the interaction between the entities.
-
E.
competitionInception
chosen
Indicates the point in time or event at which a competition is first established or begins to exist.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 3, 2026, 4:02 p.m.