Triple
T16656618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Team of Germany |
E404746
|
entity |
| Predicate | athletesCompetedAs |
P51164
|
FINISHED |
| Object | one team in medal table |
—
|
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: one team in medal table | Statement: [United Team of Germany, athletesCompetedAs, one team in medal table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: athletesCompetedAs Context triple: [United Team of Germany, athletesCompetedAs, one team in medal table]
-
A.
competedAs
chosen
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
B.
athletesFrom
Indicates that one or more athletes originate from, represent, or are associated with a particular place or organization.
-
C.
representedAthlete
Indicates that one entity serves as an official representative or agent for a particular athlete.
-
D.
hasAthlete
Indicates a relationship where an entity (such as a team, organization, or event) includes or is associated with one or more athletes.
-
E.
formerAthlete
Indicates that a person previously had the role or status of an athlete but no longer does.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfb2b308190bf3559df9fbb126f |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.