Triple
T15021490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspmyra Stadion |
E378093
|
entity |
| Predicate | hasFormerSurface |
P32808
|
FINISHED |
| Object | natural grass |
—
|
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: natural grass | Statement: [Aspmyra Stadion, hasFormerSurface, natural grass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerSurface Context triple: [Aspmyra Stadion, hasFormerSurface, natural grass]
-
A.
formerSurface
chosen
Indicates that one entity previously served as the surface or outer layer of another entity, but no longer does so.
-
B.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
-
C.
hasFormerType
Indicates that an entity previously had a certain type or classification that has since changed.
-
D.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
E.
hasFormerService
Indicates that an entity previously provided a service to another entity but no longer does so.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded765462c819097f331c9b39c80e3 |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:56 a.m.