Triple
T503980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine Road |
E10460
|
entity |
| Predicate | recordAttendanceForMatch |
P2722
|
FINISHED |
| Object | Manchester City vs Stoke City |
—
|
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: Manchester City vs Stoke City | Statement: [Maine Road, recordAttendanceForMatch, Manchester City vs Stoke City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordAttendanceForMatch Context triple: [Maine Road, recordAttendanceForMatch, Manchester City vs Stoke City]
-
A.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
B.
recordHeld
chosen
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
C.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
-
D.
teamPlayedFor
Indicates that a person was a member of and played for a particular sports team.
-
E.
numberOfGoals
Indicates the total count of goals scored or achieved by an entity 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f149bd1c81908ff58ac504ace2bf |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.