Triple
T1168201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | basketball at the 1992 Summer Olympics |
E24847
|
entity |
| Predicate | womenFinalScore |
P2625
|
FINISHED |
| Object | Unified Team 76–66 China |
—
|
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: Unified Team 76–66 China | Statement: [basketball at the 1992 Summer Olympics, womenFinalScore, Unified Team 76–66 China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: womenFinalScore Context triple: [basketball at the 1992 Summer Olympics, womenFinalScore, Unified Team 76–66 China]
-
A.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
B.
finalScoreWinner
Indicates that the referenced entity is the winner as determined by the final score of a game, match, or competition.
-
C.
reachedWNBAFinals
Indicates that an entity (typically a team) advanced to and competed in the championship series of the WNBA season.
-
D.
womenTeam
Indicates that the team is composed of women or is designated as a women’s team.
-
E.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccef84481908864e819884af86c |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.