Triple
T8696703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Police |
E206420
|
entity |
| Predicate | yearsActiveDescription |
P34676
|
FINISHED |
| Object | late 1970s to mid-1980s |
—
|
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: late 1970s to mid-1980s | Statement: [The Police, yearsActiveDescription, late 1970s to mid-1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearsActiveDescription Context triple: [The Police, yearsActiveDescription, late 1970s to mid-1980s]
-
A.
activeInYears
chosen
Indicates that an entity was active or operational during the specified years or year range.
-
B.
activeYearsInCareer
Indicates the span of time during which an entity was actively engaged in a particular career or professional field.
-
C.
historicallyActiveIn
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
-
D.
activeYearsPeak
Indicates the span of years during which an entity was at the height of its activity or prominence.
-
E.
activeInYear
Indicates that an entity was active, functioning, or operational during a specified year.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc582b04688190a439135b08e20451 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.