Triple
T9911335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derbystar football |
E185150
|
entity |
| Predicate | intendedSurface |
P1242
|
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: [Derbystar football, intendedSurface, natural grass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedSurface Context triple: [Derbystar football, intendedSurface, natural grass]
-
A.
usesSurface
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
-
B.
surfaceOrientation
Indicates the spatial orientation or facing direction of a surface relative to a reference frame or viewpoint.
-
C.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
D.
surfaceType
chosen
Indicates the kind or classification of surface associated with an entity or interaction.
-
E.
intendedView
Indicates that one entity is the target or preferred perspective, representation, or display mode through which another entity is meant to be viewed or presented.
- 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb512a26881908eb72a21ffb1efef |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.