Triple
T7117920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1934 VFL premiership |
E165865
|
entity |
| Predicate | margin |
P66013
|
FINISHED |
| Object | 39 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: 39 points | Statement: [1934 VFL premiership, margin, 39 points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: margin Context triple: [1934 VFL premiership, margin, 39 points]
-
A.
marginOf
chosen
Indicates the difference or buffer between two related quantities, values, or boundaries, often expressing how much one exceeds or falls short of another.
-
B.
margining
Indicates the process of posting, adjusting, or settling collateral (margin) between parties to secure obligations in a financial transaction or trading relationship.
-
C.
marginSystem
Indicates a financial arrangement where securities are bought or held using borrowed funds, with the securities themselves serving as collateral under a defined margin framework.
-
D.
marginType
Indicates the type or category of margin applied in a given context, such as financial, layout, or safety margin.
-
E.
marginEfficiency
Indicates how effectively the margin between revenue and costs is generated or utilized in a given context.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e618bdac8190be291468b7d977bb |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.