Triple
T11100033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UDDF |
E262477
|
entity |
| Predicate | dataCategory |
P87
|
FINISHED |
| Object | technical sports data |
—
|
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: technical sports data | Statement: [UDDF, dataCategory, technical sports data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCategory Context triple: [UDDF, dataCategory, technical sports data]
-
A.
textCategory
Indicates that a piece of text belongs to or is classified under a particular category or type.
-
B.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
C.
categoryExample
Indicates that something is an example or instance illustrating a particular category.
-
D.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
E.
categoryLabel_N
Indicates that an entity is assigned a specific categorical label or classification name.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a29ee6c819092bc0da3f9255389 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.