Triple
T7756980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greco-Roman wrestling |
E175921
|
entity |
| Predicate | teamFormat |
P78540
|
FINISHED |
| Object | individual bouts contributing to team score |
—
|
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: individual bouts contributing to team score | Statement: [Greco-Roman wrestling, teamFormat, individual bouts contributing to team score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamFormat Context triple: [Greco-Roman wrestling, teamFormat, individual bouts contributing to team score]
-
A.
teamFormatHistory
Indicates the historical record of changes or versions in a team's structural or competitive format over time.
-
B.
teamStyle
Indicates the characteristic way a team typically operates, collaborates, and approaches its work or objectives.
-
C.
teamRepresentation
Indicates that one entity serves as the official representative or embodiment of a team in a given context or activity.
-
D.
teamName
Indicates the relationship that assigns or associates a specific name with a particular team.
-
E.
leagueTeam2
Indicates that the subject entity is the second team participating in a particular league, matchup, or league-related context.
- 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c70524c3948190a163dc5f4ecdffa7 |
completed | March 27, 2026, 10:31 p.m. |
Created at: March 27, 2026, 4:09 p.m.