Triple
T3379585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic Games Marathon |
E71148
|
entity |
| Predicate | teamComponent |
P47487
|
FINISHED |
| Object | medals awarded to individuals, not teams |
—
|
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: medals awarded to individuals, not teams | Statement: [Olympic Games Marathon, teamComponent, medals awarded to individuals, not teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamComponent Context triple: [Olympic Games Marathon, teamComponent, medals awarded to individuals, not teams]
-
A.
team
Indicates that multiple entities are grouped together as a collaborative unit working toward shared goals or tasks.
-
B.
memberTeam
Indicates that an entity belongs to or is part of a specific team.
-
C.
teamBuilt
Indicates that one entity created, assembled, or established a team that includes or is composed of another entity.
-
D.
team1
Indicates that the referenced entity is the first team or side participating in a competitive or relational context.
-
E.
team2
Indicates that the second team involved in a competitive or collaborative context is associated with a given entity or event.
- F. None of above. chosen
Provenance (4 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2ec38d88190be8c824daeca5ab6 |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:14 p.m.