Triple
T8688296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1860 Munich |
E206220
|
entity |
| Predicate | traditionalClubStatus |
P84190
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [1860 Munich, traditionalClubStatus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalClubStatus Context triple: [1860 Munich, traditionalClubStatus, yes]
-
A.
isTraditionalClubIn
Indicates that a club is traditionally associated with or located in a particular place or region.
-
B.
originalMemberClub
Indicates that an entity was one of the initial or founding members of a particular club.
-
C.
isPrivateClub
Indicates that the entity functions as a club or organization that restricts membership or access to a select, non-public group of people.
-
D.
ownerClub
Indicates that a particular club is the owning or parent organization of a given entity (such as a team, facility, or asset).
-
E.
clubMembership
Indicates that an entity belongs to, is enrolled in, or holds membership status within a particular club.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5731cf08819082e0cbe0975b70bb |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc483f06f48190879f4702c8b4ed00 |
completed | March 31, 2026, 10:18 p.m. |
Created at: March 30, 2026, 6:33 p.m.