Triple
T32578369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coolray Field |
E832710
|
entity |
| Predicate | servedByTeamSince |
P22450
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Coolray Field, servedByTeamSince, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByTeamSince Context triple: [Coolray Field, servedByTeamSince, 2009]
-
A.
memberTeamAtVariousTimes
Indicates that an entity has been a member of a particular team during one or more distinct time periods.
-
B.
debutedAsTeam
Indicates that an entity made its first official appearance or start in a particular context as a member of a specified team.
-
C.
homeTeamSince
chosen
Indicates the point in time from which a particular team has been designated as the home team for a given context or venue.
-
D.
teamCoachedFromTo
Indicates a coaching relationship where a person served as coach of a team during a specific time interval from a start date to an end date.
-
E.
operatedAsProfessionalTeamUntil
Indicates that an entity functioned in the capacity of a professional team up to a specified end point in time.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: May 1, 2026, 1:04 a.m.