Triple
T14747096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997 Super League Grand Final |
E346499
|
entity |
| Predicate | resultMargin |
P39190
|
FINISHED |
| Object | 18 points |
—
|
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: 18 points | Statement: [1997 Super League Grand Final, resultMargin, 18 points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultMargin Context triple: [1997 Super League Grand Final, resultMargin, 18 points]
-
A.
marginOf
Indicates the difference or buffer between two related quantities, values, or boundaries, often expressing how much one exceeds or falls short of another.
-
B.
finalRoundMargin
chosen
Indicates the point or score difference between competitors in the final round of a contest or competition.
-
C.
margining
Indicates the process of posting, adjusting, or settling collateral (margin) between parties to secure obligations in a financial transaction or trading relationship.
-
D.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
-
E.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d116e88190828b163b18d80f68 |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.