Triple
T35176495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balmain Tigers |
E1015718
|
entity |
| Predicate | mergerEffectiveFromSeason |
P176
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Balmain Tigers, mergerEffectiveFromSeason, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerEffectiveFromSeason Context triple: [Balmain Tigers, mergerEffectiveFromSeason, 2000]
-
A.
acquisitionEffectiveSeason
Indicates the season during which an acquisition becomes officially effective or takes effect.
-
B.
leagueMergerAfterSeasonWith
Indicates that two or more leagues merged into a single league following the completion of a specified season.
-
C.
mergerPeriod
Indicates the time span during which two or more entities are in the process of merging into a single combined entity.
-
D.
hasMergerEffectiveDate
Indicates the date on which a merger between entities becomes legally effective and operational.
-
E.
mergerYear
chosen
Indicates the year in which two or more entities formally merged into a single entity.
- 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_69f78d76f65c81908af6b116e3eedb12 |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.