Triple
T35984560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sereno Soccer Club |
E1040674
|
entity |
| Predicate | playersProgressTo |
P25302
|
FINISHED |
| Object | college soccer programs |
—
|
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: college soccer programs | Statement: [Sereno Soccer Club, playersProgressTo, college soccer programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playersProgressTo Context triple: [Sereno Soccer Club, playersProgressTo, college soccer programs]
-
A.
playerProgressionFrom
chosen
Indicates a progression or advancement of a player from one state, level, or stage to another.
-
B.
progressionPosition
Indicates the specific place or rank that something occupies within an ordered sequence, series, or progression.
-
C.
multiplayerProgression
Indicates that multiple participants advance or develop together over time within a shared activity or system.
-
D.
playedUntil
Indicates that an action or event involving playing continued up to a specific time, point, or condition.
-
E.
playedProfessionalUntil
Indicates that an entity participated in a professional-level activity or career up to and including a specified end time or date.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 3, 2026, 4:07 p.m.