Triple
T33921617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thurrock F.C. (temporary) |
E869628
|
entity |
| Predicate | homeMatchesStatus |
P178124
|
FINISHED |
| Object | played away from usual 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: played away from usual ground | Statement: [Thurrock F.C. (temporary), homeMatchesStatus, played away from usual ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeMatchesStatus Context triple: [Thurrock F.C. (temporary), homeMatchesStatus, played away from usual ground]
-
A.
hostedHomeMatchesFor
Indicates that an entity organized and held competitive matches at its own home venue for another entity or group.
-
B.
homeMatchesCountry
Indicates that an entity’s home location is situated within the specified country.
-
C.
homeMatchesWatched
Indicates that the number or set of home matches corresponds to those that have been watched.
-
D.
homeMatchesRegion
Indicates that an entity’s home location is situated within or corresponds to a specified geographic region.
-
E.
homeMatchType
Indicates the type or category of match in which an entity is designated as the home side.
- F. None of above. chosen
Provenance (4 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:49 a.m.