Triple
T25457944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadion An der Alten Försterei |
E637963
|
entity |
| Predicate | supporterVolunteersInRenovation |
P138783
|
FINISHED |
| Object | over 2,000 |
—
|
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: over 2,000 | Statement: [Stadion An der Alten Försterei, supporterVolunteersInRenovation, over 2,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supporterVolunteersInRenovation Context triple: [Stadion An der Alten Försterei, supporterVolunteersInRenovation, over 2,000]
-
A.
usesVolunteers
chosen
Indicates that an entity relies on or engages volunteers to perform its activities or services.
-
B.
supporter
Indicates a relationship where one entity backs, advocates for, or provides assistance to another entity, often in an ongoing or affiliative way.
-
C.
supporters
Indicates a relationship where one entity backs, endorses, or actively helps another entity, cause, or position.
-
D.
supportersDescription
Indicates that one entity provides support, endorsement, or backing to another entity.
-
E.
supportersAdded
Indicates that one or more supporters have been newly associated with or added to an entity or activity.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 21, 2026, 2:10 p.m.