Triple
T33885449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Cranleighan Sports Club |
E868618
|
entity |
| Predicate | hasTypeOfGround |
P194417
|
FINISHED |
| Object | outdoor sports ground |
—
|
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: outdoor sports ground | Statement: [Old Cranleighan Sports Club, hasTypeOfGround, outdoor sports ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfGround Context triple: [Old Cranleighan Sports Club, hasTypeOfGround, outdoor sports ground]
-
A.
hasGround
Indicates that one entity possesses, is supported by, or is associated with a ground or base surface.
-
B.
hasTypeOfGrounds
chosen
Indicates that an entity possesses or is associated with a specific kind or category of grounds (e.g., land, surface, or terrain type).
-
C.
hasGroundPressure
Indicates that an entity exerts a specific amount of pressure on the ground or surface it is in contact with.
-
D.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
-
E.
usesGroundFor
Indicates that one entity makes functional or practical use of a particular ground, surface, or land area for its activities or purposes.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: May 1, 2026, 1:48 a.m.