Triple
T16061231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | synchronized swimming at the 2008 Summer Olympics |
E389615
|
entity |
| Predicate | isTeamBased |
P33195
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [synchronized swimming at the 2008 Summer Olympics, isTeamBased, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTeamBased Context triple: [synchronized swimming at the 2008 Summer Olympics, isTeamBased, yes]
-
A.
isTeamSpecific
Indicates that something applies only to, or is restricted to, a particular team rather than being general or shared across multiple teams.
-
B.
teamBased
chosen
Indicates that an activity, process, or structure is organized around collaboration within a group or team rather than by individuals working independently.
-
C.
teamBasedOn
Indicates that one entity (typically a team) is formed, organized, or defined on the basis of another entity (such as a criterion, source, or underlying structure).
-
D.
isTeamConstruct
Indicates that an entity is a constructed or assembled team, rather than a naturally occurring or default group.
-
E.
includesTeam
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.