Triple
T9805929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TUDN |
E237952
|
entity |
| Predicate | primaryContentRegion |
P90077
|
FINISHED |
| Object | Latin American sports |
—
|
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: Latin American sports | Statement: [TUDN, primaryContentRegion, Latin American sports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryContentRegion Context triple: [TUDN, primaryContentRegion, Latin American sports]
-
A.
primaryContent
Indicates that one entity serves as the main or most important content associated with another entity.
-
B.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
-
C.
primaryMedium
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
-
D.
primaryView
Indicates that one view or representation is designated as the main or default perspective among multiple possible views of the same entity or content.
-
E.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7b67748190ba16ce868f29d13e |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:29 p.m.