Triple
T30063673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weserstadion |
E763964
|
entity |
| Predicate | hasRegulationField |
P202083
|
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: [Weserstadion, hasRegulationField, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegulationField Context triple: [Weserstadion, hasRegulationField, yes]
-
A.
hasRegulationFieldShape
Indicates that something is characterized by or associated with a particular shape in the context of regulation.
-
B.
hasRegulations
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
C.
regulatoryField
Indicates that one entity operates within, is governed by, or is associated with a particular area or domain of regulation defined by another entity.
-
D.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
E.
hasRegulationScope
Indicates that a regulation applies to, or governs, a specified scope, domain, or area of relevance.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
| PDg | Predicate description generation | batch_6a004d0a95548190ac822cd1d54edf42 |
completed | May 10, 2026, 9:16 a.m. |
Created at: April 29, 2026, 6:58 p.m.