Triple
T37998638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyari |
E948029
|
entity |
| Predicate | hasNotableFootballClubs |
P111529
|
FINISHED |
| Object | localFootballClubs |
—
|
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: localFootballClubs | Statement: [Lyari, hasNotableFootballClubs, localFootballClubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFootballClubs Context triple: [Lyari, hasNotableFootballClubs, localFootballClubs]
-
A.
notableClubsInclude
chosen
Indicates that the specified clubs are among the particularly significant or well-known clubs associated with the given entity.
-
B.
hasSportsClubs
Indicates that an entity possesses, hosts, or is associated with one or more sports clubs.
-
C.
hasNotableSportAssociation
Indicates a relationship where an entity is significantly connected to, recognized for, or prominently involved with a particular sport or sports organization.
-
D.
hasNotableClubGroup
Indicates that an entity is associated with a significant or distinguished club or group.
-
E.
hasProfessionalClubs
Indicates that there exists a professional sports or activity club associated with, based in, or belonging to the given entity.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.