Triple
T2514199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Top Billboard 200 Album |
E52771
|
entity |
| Predicate | hasMeasurementPeriod |
P34855
|
FINISHED |
| Object | one-year eligibility period |
—
|
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: one-year eligibility period | Statement: [Top Billboard 200 Album, hasMeasurementPeriod, one-year eligibility period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeasurementPeriod Context triple: [Top Billboard 200 Album, hasMeasurementPeriod, one-year eligibility period]
-
A.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
B.
hasCountingPeriod
chosen
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
-
C.
hasDiscoveryPeriod
Indicates the time span during which a particular discovery was made or recognized.
-
D.
measuredAt
Indicates the time or point at which a measurement was taken or recorded for an entity or event.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.