Triple
T27860175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jimmy Sirrel Stand |
E704203
|
entity |
| Predicate | locatedOnGround |
P56549
|
FINISHED |
| Object | Meadow Lane pitch perimeter |
—
|
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: Meadow Lane pitch perimeter | Statement: [Jimmy Sirrel Stand, locatedOnGround, Meadow Lane pitch perimeter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnGround Context triple: [Jimmy Sirrel Stand, locatedOnGround, Meadow Lane pitch perimeter]
-
A.
locatedOnTerrain
chosen
Indicates that one entity is physically situated on or atop a particular terrain surface.
-
B.
usesGroundFor
Indicates that one entity makes functional or practical use of a particular ground, surface, or land area for its activities or purposes.
-
C.
locatedAboveGround
Indicates that one entity is positioned at a level higher than the ground surface, not buried or below ground.
-
D.
hasGround
Indicates that one entity possesses, is supported by, or is associated with a ground or base surface.
-
E.
isGroundedIn
Indicates that something is based on, supported by, or justified through a particular source, foundation, or set of principles.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: April 27, 2026, 6:17 p.m.