Triple
T26395813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fauldhouse United F.C. |
E663548
|
entity |
| Predicate | playsSeasonally |
P1166
|
FINISHED |
| Object | August to May |
—
|
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: August to May | Statement: [Fauldhouse United F.C., playsSeasonally, August to May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsSeasonally Context triple: [Fauldhouse United F.C., playsSeasonally, August to May]
-
A.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
B.
seasonCycle
Indicates a recurring pattern or sequence of seasons or seasonal phases that repeat over time.
-
C.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
D.
season
chosen
Indicates that an entity participates in, is associated with, or occurs during a particular season or seasonal period.
-
E.
hasSeasonalRound
Indicates a recurring, seasonally patterned cycle of movements, activities, or resource use associated with an entity over the course of a year.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 11:28 p.m.