Triple
T13532339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAM |
E323163
|
entity |
| Predicate | hasSportCodeRole |
P50040
|
FINISHED |
| Object | team identifier |
—
|
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: team identifier | Statement: [TAM, hasSportCodeRole, team identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportCodeRole Context triple: [TAM, hasSportCodeRole, team identifier]
-
A.
isInSportSystemOf
Indicates that one entity belongs to, is organized within, or operates under the structure of a particular sport system or sports organizational framework of another entity.
-
B.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
C.
sportCode
chosen
Indicates the specific sport associated with or classified for an entity, typically via a standardized code or identifier.
-
D.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
E.
hasRelativeInSport
Indicates that one entity has a family member who participates or is involved in a sport-related activity or profession.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbb34548190a6b44faa48125cd4 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.