Triple
T35403106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orlando City SC vs Sacramento Republic FC |
E1023288
|
entity |
| Predicate | homeTeamCountryCode |
P152237
|
FINISHED |
| Object | USA |
—
|
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: USA | Statement: [Orlando City SC vs Sacramento Republic FC, homeTeamCountryCode, USA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamCountryCode Context triple: [Orlando City SC vs Sacramento Republic FC, homeTeamCountryCode, USA]
-
A.
awayTeamCountryCode
Indicates the country code associated with the away (visiting) team in a match or event.
-
B.
hasHomeTeamCountry
Indicates that an entity representing a sports match or event is associated with the country of its designated home team.
-
C.
homeCountryTeamOf
Indicates that one entity is the national team representing the home country of another entity.
-
D.
homeCountryForLeaguePurposes
Indicates the country that is officially recognized as a league’s home or base of operations for regulatory or organizational purposes.
-
E.
homeTeamFIFAcode
chosen
Indicates the FIFA country code assigned to the team designated as the home team in a match.
- 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.