Triple
T27086957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greco-Roman |
E686059
|
entity |
| Predicate | teamScoringUsage |
P162049
|
FINISHED |
| Object | used in dual meets and team tournaments |
—
|
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: used in dual meets and team tournaments | Statement: [Greco-Roman, teamScoringUsage, used in dual meets and team tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamScoringUsage Context triple: [Greco-Roman, teamScoringUsage, used in dual meets and team tournaments]
-
A.
teamScoring
Indicates that a team achieves a score or points in a game, match, or competitive event.
-
B.
topTryScorerTeam
Indicates that a team is the one for which a given player is the top try scorer.
-
C.
teamAchievement
Indicates that a group of individuals collectively accomplished a shared goal or met a performance milestone.
-
D.
leagueScoringRecord
Indicates that an entity holds the record for the highest scoring performance or total within a particular league.
-
E.
totalPointsScored
Indicates the total number of points accumulated or scored by an entity over a defined period, event, or 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6234735cc819097c3f109e724b0a4 |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621c7d3e0819095b1f327637ae4f9 |
completed | May 2, 2026, 4:09 p.m. |
Created at: April 27, 2026, 8:38 a.m.