Triple
T36025393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EC Bad Nauheim |
E1042112
|
entity |
| Predicate | hasArenaCapacity |
P196803
|
FINISHED |
| Object | approximately 4000 |
—
|
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: approximately 4000 | Statement: [EC Bad Nauheim, hasArenaCapacity, approximately 4000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArenaCapacity Context triple: [EC Bad Nauheim, hasArenaCapacity, approximately 4000]
-
A.
hasStandingCapacity
Indicates that an entity is capable of maintaining or supporting a specified condition, function, or load on an ongoing basis.
-
B.
hasHomeCapacityVenue
Indicates that a venue has a specified capacity for accommodating people or events as its home location.
-
C.
hasCapacityIncludingStanding
Indicates that an entity’s total capacity includes both seated and standing occupants.
-
D.
playerCapacity
Indicates the maximum number of players that can simultaneously participate in or be accommodated by something (such as a game, session, or venue).
-
E.
hasLocalArena
Indicates that an entity possesses or is associated with an arena or venue located within its local area or jurisdiction.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
| PDg | Predicate description generation | batch_69fe68a385f48190b942700e3eddc9b6 |
completed | May 8, 2026, 10:50 p.m. |
Created at: May 3, 2026, 4:07 p.m.