Triple
T16290081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seddon Park |
E395494
|
entity |
| Predicate | outfield |
P107912
|
FINISHED |
| Object | fast |
—
|
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: fast | Statement: [Seddon Park, outfield, fast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outfield Context triple: [Seddon Park, outfield, fast]
-
A.
outfieldSurface
chosen
Indicates the type or condition of the playing surface specifically in the outfield area of a sports field.
-
B.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
-
C.
fielded
Indicates that an entity deployed, presented, or put forward another entity (such as a person, team, or resource) for participation or use in a particular context or activity.
-
D.
leftFielder
Indicates the relationship where an entity serves in the defensive baseball position of left fielder for a team or in a specific game context.
-
E.
fieldedIn
Indicates that an entity was deployed, presented, or put into active use within a particular context, event, or domain.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e249175e24819082e571039e278056 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.