Triple
T9910250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Championnat National |
E185121
|
entity |
| Predicate | matchOutcomePointsSystem |
P24875
|
FINISHED |
| Object | three points for a win |
—
|
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: three points for a win | Statement: [Championnat National, matchOutcomePointsSystem, three points for a win]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchOutcomePointsSystem Context triple: [Championnat National, matchOutcomePointsSystem, three points for a win]
-
A.
matchPointsDraw
Indicates that the entities receive or share an equal number of points as a result of a drawn or tied match.
-
B.
pointsForWin
chosen
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
C.
pointsForShootoutWin
Indicates the number of points awarded to a team for winning a game via a shootout.
-
D.
playoffPoints
Indicates the number of points an entity has earned or been credited with in playoff or postseason competition.
-
E.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb51184d08190a0350f2722110811 |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.