Triple
T1132335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notts County F.C. |
E23058
|
entity |
| Predicate | playsInSystem |
P25330
|
FINISHED |
| Object | English football league system |
—
|
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: English football league system | Statement: [Notts County F.C., playsInSystem, English football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsInSystem Context triple: [Notts County F.C., playsInSystem, English football league system]
-
A.
playsOn
Indicates that one entity participates or performs on a particular team, platform, or medium.
-
B.
isPlayedIn
Indicates that an instance of a game, sport, or performance takes place within or is hosted at a particular location or venue.
-
C.
playsInPosition
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
D.
plays
Indicates that an entity engages in or performs an activity, game, role, or piece of music.
-
E.
playsOnSurface
Indicates that an entity performs or engages in an activity while being in contact with or supported by a particular surface.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc47fce48190825d3a877251f789 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:44 p.m.