Triple
T31477014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balgarska Armia Stadium |
E803021
|
entity |
| Predicate | hasTypeOfStands |
P31102
|
FINISHED |
| Object | all-seater (predominantly) |
—
|
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: all-seater (predominantly) | Statement: [Balgarska Armia Stadium, hasTypeOfStands, all-seater (predominantly)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfStands Context triple: [Balgarska Armia Stadium, hasTypeOfStands, all-seater (predominantly)]
-
A.
hasStandsType
chosen
Indicates that an entity has or is associated with a particular type or category of stands (e.g., display stands, support stands, or similar structures).
-
B.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
C.
isStandOf
Indicates that one entity serves as the Stand (a supernatural or personified power) belonging to or associated with another entity.
-
D.
hasStationTypeAt
Indicates that a specific type of station is present or assigned at a particular location or point.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: April 30, 2026, 9:29 p.m.