Triple
T6898933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celtic Park stands |
E159442
|
entity |
| Predicate | surfaceView |
P74008
|
FINISHED |
| Object | Celtic Park pitch |
—
|
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: Celtic Park pitch | Statement: [Celtic Park stands, surfaceView, Celtic Park pitch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceView Context triple: [Celtic Park stands, surfaceView, Celtic Park pitch]
-
A.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
B.
surfaceState
Indicates the physical condition or status of a surface, such as its texture, cleanliness, damage, or treatment at a given time.
-
C.
surfaceCurrent
Indicates that one entity is the prevailing flow or movement of a fluid (such as water or air) along the surface of another entity.
-
D.
surfaceChange
Indicates a change in the physical surface characteristics or condition of an entity over time or due to some event or interaction.
-
E.
usesSurface
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95d67448190857f36b8115b03f6 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:24 p.m.