Triple
T35403099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orlando City SC vs Sacramento Republic FC |
E1023288
|
entity |
| Predicate | awayClubFullName |
P118509
|
FINISHED |
| Object | Sacramento Republic Football Club |
—
|
NE NERFINISHED |
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: Sacramento Republic Football Club | Statement: [Orlando City SC vs Sacramento Republic FC, awayClubFullName, Sacramento Republic Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awayClubFullName Context triple: [Orlando City SC vs Sacramento Republic FC, awayClubFullName, Sacramento Republic Football Club]
-
A.
awayClub
chosen
Indicates that one entity is the club playing as the visiting (away) team in a sports match or event relative to another entity.
-
B.
awayClubLeague
Indicates the league or competition in which the away (visiting) club participates.
-
C.
homeClubFullName
Indicates the full official name of the club that serves as the home team in the given context.
-
D.
affiliatedClubOf
Indicates that one entity is a club with which another entity is formally associated or connected.
-
E.
alternativeNameOfClub
Indicates that one club is an alternative or secondary name/designation for another club.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.