Triple
T22393647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roadrunner |
E553573
|
entity |
| Predicate | representsTeamsInSport |
P112147
|
FINISHED |
| Object | basketball |
—
|
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: basketball | Statement: [Roadrunner, representsTeamsInSport, basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsTeamsInSport Context triple: [Roadrunner, representsTeamsInSport, basketball]
-
A.
representsTeamsIn
chosen
Indicates that one entity serves as a representative or agent on behalf of a team or multiple teams.
-
B.
representsTeamsNamed
Indicates that two or more entities are associated with teams that share the same name.
-
C.
representsInLeague
Indicates that an entity serves as a representative of another entity within a specific league or organized competition.
-
D.
representsInSport
Indicates that one entity serves as an official representative of another entity within the context of a particular sport or sporting domain.
-
E.
tournamentRepresented
Indicates that an entity serves as the official representation or depiction of a particular tournament (e.g., as its model, record, or formal instance).
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1585ce39c819082b62e7f2e297d9b |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.