Triple
T1339256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serie A |
E28425
|
entity |
| Predicate | tieBreakerCriterion |
P6631
|
FINISHED |
| Object | head-to-head record |
—
|
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: head-to-head record | Statement: [Serie A, tieBreakerCriterion, head-to-head record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieBreakerCriterion Context triple: [Serie A, tieBreakerCriterion, head-to-head record]
-
A.
tiebreaker
chosen
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
B.
targetScoreRule
Indicates the rule or criteria used to determine the target score to be achieved or applied in a given context.
-
C.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
D.
thresholdFor
Indicates that one entity specifies the minimum or limiting value at which a condition, effect, or state involving another entity begins to occur or change.
-
E.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c21303c881908fef0b32831222fe |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.