Triple
T11278623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertha BSC |
E267002
|
entity |
| Predicate | historicClub |
P36696
|
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: [Hertha BSC, historicClub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicClub Context triple: [Hertha BSC, historicClub, true]
-
A.
historicFor
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
B.
sportsHeritage
chosen
Indicates a relationship where one entity preserves, represents, or is associated with the historical traditions, legacy, or cultural heritage of a sport or sporting community.
-
C.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
D.
historicPlayer
Indicates that an entity is recognized as a notable player from the past, typically associated with historical significance in its domain.
-
E.
historicCore
Indicates that something is part of, located within, or associated with the original historic center or oldest developed area of a place.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e967ebb4819080b09ed3cec44e77 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.