Triple
T27519269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East German football league system |
E694659
|
entity |
| Predicate | includedPoliceClubParticipation |
P145401
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [East German football league system, includedPoliceClubParticipation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedPoliceClubParticipation Context triple: [East German football league system, includedPoliceClubParticipation, true]
-
A.
hasPlayedWithClub
Indicates that an individual has been a member of and participated in activities or competitions for a particular club.
-
B.
involvesClub
Indicates that an action, event, or relationship includes or is associated with a specific club as a participating entity.
-
C.
hadMemberClubsIn
chosen
Indicates that an organization or group possessed member clubs located within a specified place or jurisdiction.
-
D.
representedClub
Indicates that an entity has acted as a representative of, or played for, a particular club or team.
-
E.
usedByClub
Indicates that something (such as a resource, facility, or item) is utilized or employed by a club.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 27, 2026, 1:20 p.m.