Triple
T2288687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Top Latin Artist |
E51452
|
entity |
| Predicate | trackingPeriod |
P302
|
FINISHED |
| Object | Billboard Music Awards eligibility year |
—
|
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: Billboard Music Awards eligibility year | Statement: [Top Latin Artist, trackingPeriod, Billboard Music Awards eligibility year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackingPeriod Context triple: [Top Latin Artist, trackingPeriod, Billboard Music Awards eligibility year]
-
A.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
C.
focusPeriod
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
D.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
-
E.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc2497ce881909b05eb9cec67d9e7 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.