Triple
T34221283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Hemisphere and South Africa |
E877927
|
entity |
| Predicate | includesLeagueTeamsFrom |
P198160
|
FINISHED |
| Object | Ireland |
E5475
|
NE 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: Ireland | Statement: [Northern Hemisphere and South Africa, includesLeagueTeamsFrom, Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLeagueTeamsFrom Context triple: [Northern Hemisphere and South Africa, includesLeagueTeamsFrom, Ireland]
-
A.
includesLeague
Indicates that an entity (such as a competition, organization, or system) contains or encompasses a specific league as one of its components.
-
B.
associatedLeagueTeam
Indicates that one entity is a sports team that is formally linked or affiliated with a particular league.
-
C.
includesClubFromLeague
chosen
Indicates that a collection or group contains at least one club that belongs to a specified league.
-
D.
leagueWithTeam
Indicates that a league is associated with, includes, or is composed of a particular team.
-
E.
leagueAddedTeams
Indicates that one or more teams have been newly added to a league.
- F. None of above.
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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36cc79fee88190ac0692378a5b9996 |
completed | June 20, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:55 a.m.