Triple
T3375292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brisbane Bears |
E71051
|
entity |
| Predicate | mergerOutcome |
P15102
|
FINISHED |
| Object | creation of Brisbane Lions Football Club |
—
|
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: creation of Brisbane Lions Football Club | Statement: [Brisbane Bears, mergerOutcome, creation of Brisbane Lions Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerOutcome Context triple: [Brisbane Bears, mergerOutcome, creation of Brisbane Lions Football Club]
-
A.
mergerResult
chosen
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
-
B.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
C.
mergerSettlement
Indicates a legal or financial resolution reached between parties involved in a merger, typically settling disputes or claims arising from the merger transaction.
-
D.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
E.
dissolvedByMerger
Indicates that an entity ceased to exist as an independent entity because it was legally combined into another entity through a merger.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e5fc6c81909ff582611751096d |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.