Triple
T8324523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watton-at-Stone |
E194915
|
entity |
| Predicate | hasPlayingField |
P33887
|
FINISHED |
| Object | Watton-at-Stone village green |
—
|
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: Watton-at-Stone village green | Statement: [Watton-at-Stone, hasPlayingField, Watton-at-Stone village green]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayingField Context triple: [Watton-at-Stone, hasPlayingField, Watton-at-Stone village green]
-
A.
hasPlayAreaType
Indicates the specific kind or category of play area associated with an entity (e.g., indoor, outdoor, playground type).
-
B.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
C.
hasPhaseOfPlay
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
-
D.
hasSportsGround
chosen
Indicates that an entity possesses, includes, or is associated with a sports ground or athletic field as part of its facilities or area.
-
E.
homeSoccerField
Indicates that a particular soccer field serves as the designated home field for a given team or organization.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f7e4f8081908e0f876ad962c932 |
completed | March 31, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.