Triple
T11753680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple (Der Tempel) |
E279469
|
entity |
| Predicate | reflectsStatusOf |
P45754
|
FINISHED |
| Object | Signal Iduna Park in German football culture |
—
|
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: Signal Iduna Park in German football culture | Statement: [Temple (Der Tempel), reflectsStatusOf, Signal Iduna Park in German football culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsStatusOf Context triple: [Temple (Der Tempel), reflectsStatusOf, Signal Iduna Park in German football culture]
-
A.
impliesStatus
Indicates that one condition, fact, or state logically leads to or determines another status or outcome.
-
B.
obtainedStatus
Indicates that an entity has received or achieved a particular status or condition as a result of some process or event.
-
C.
recognizesStatus
Indicates that one entity acknowledges or accepts the official status or standing of another entity.
-
D.
associatedStatus
chosen
Indicates that one entity is linked to or characterized by a particular status or condition.
-
E.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50b8a14819092a7397d73f0a8e3 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.