Triple
T6260967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorking Wanderers F.C. |
E140295
|
entity |
| Predicate | movedToGround |
P42451
|
FINISHED |
| Object | Meadowbank Stadium in 2018 |
—
|
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: Meadowbank Stadium in 2018 | Statement: [Dorking Wanderers F.C., movedToGround, Meadowbank Stadium in 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedToGround Context triple: [Dorking Wanderers F.C., movedToGround, Meadowbank Stadium in 2018]
-
A.
previousGround
Indicates that one entity is the immediately preceding ground or surface state relative to another in a sequence or progression.
-
B.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
-
C.
brokeGround
Indicates that an entity initiated construction or development on a site, typically by starting physical work such as excavation or foundation laying.
-
D.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
-
E.
movementLocation
chosen
Indicates a relationship where an entity moves to, from, or through a specified location.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063856f308190a351a661caaae5f9 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.