Triple
T1339255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serie A |
E28425
|
entity |
| Predicate | homeAndAwayMatchesPerTeam |
P27340
|
FINISHED |
| Object | 38 |
—
|
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: 38 | Statement: [Serie A, homeAndAwayMatchesPerTeam, 38]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeAndAwayMatchesPerTeam Context triple: [Serie A, homeAndAwayMatchesPerTeam, 38]
-
A.
playedHomeMatchesIn
Indicates that an entity (typically a sports team) hosted its home matches at a specified venue or location.
-
B.
homeTeamSince
Indicates the point in time from which a particular team has been designated as the home team for a given context or venue.
-
C.
goalsHomeTeam
Indicates the number of goals scored by the home team in a match.
-
D.
clubAppearances
Indicates the number of official matches a player has played for a particular club.
-
E.
homeTeamUntil
Indicates that an entity serves as the home team for another entity up to (but not necessarily after) a specified time or event.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a4c06721488190ac7f6e012f21af3d |
completed | March 1, 2026, 10:40 p.m. |
Created at: March 1, 2026, 7:56 p.m.