Triple
T37438738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertha BSC II |
E930350
|
entity |
| Predicate | isReserveSideOf |
P40723
|
FINISHED |
| Object | Hertha BSC |
—
|
NE NERFINISHED |
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: Hertha BSC | Statement: [Hertha BSC II, isReserveSideOf, Hertha BSC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReserveSideOf Context triple: [Hertha BSC II, isReserveSideOf, Hertha BSC]
-
A.
hasReserveSideIn
Indicates that an entity serves as the reserve or backup side within a specified context, location, or configuration.
-
B.
isReserveComponentOf
chosen
Indicates that one entity serves as a backup, auxiliary, or reserve part or resource for another entity, to be used when the primary is unavailable or insufficient.
-
C.
isBSideOf
Indicates that one entity is located on the B side or secondary face of another entity, typically in a two-sided or dual-orientation context.
-
D.
isOneOfSidesOf
Indicates that an entity is one of the boundary edges or lateral faces that form part of another entity.
-
E.
isPrimaryReserveOf
Indicates that one entity serves as the main or principal reserve (backup or stored resource) for another 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.