Triple
T24318836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh City F.C. |
E612897
|
entity |
| Predicate | playsDomesticLeague |
P155543
|
FINISHED |
| Object | Scottish Professional Football League |
—
|
NE NERFINISHED |
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: Scottish Professional Football League | Statement: [Edinburgh City F.C., playsDomesticLeague, Scottish Professional Football League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsDomesticLeague Context triple: [Edinburgh City F.C., playsDomesticLeague, Scottish Professional Football League]
-
A.
domesticLeagueTitle
Indicates that an entity has won a championship title in its primary national (domestic) league competition.
-
B.
domesticLeagueOrganizer
Indicates that an entity is responsible for organizing or administering a domestic sports league.
-
C.
playedDomesticTeam
Indicates that an athlete has been a member of or has competed for a particular domestic (non-international) team.
-
D.
countryLeagueScope
Indicates that a league’s scope or coverage is defined at the level of a specific country.
-
E.
hostsLeague
Indicates that one entity serves as the organizing or venue-providing host for a particular league.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292aa63fc8190a874367c9010f283 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:47 a.m.