Triple
T32364415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Legend singles chronology |
E826951
|
entity |
| Predicate | hasFirstKnownEra |
P113262
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [John Legend singles chronology, hasFirstKnownEra, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstKnownEra Context triple: [John Legend singles chronology, hasFirstKnownEra, early 2000s]
-
A.
hasPrimaryEra
Indicates that an entity is chiefly associated with or belongs to a particular historical or temporal era.
-
B.
hasEraYearCount
Indicates the total number of years encompassed by a particular era or period.
-
C.
hasEraReset
Indicates that a new era or time period has been initiated, resetting the previous temporal sequence or counting.
-
D.
hasEraSignificance
Indicates that something holds notable importance, influence, or relevance within a particular historical era or time period.
-
E.
earliestKnownPeriod
chosen
Indicates the earliest historical or temporal period in which the subject is known or documented to have existed, occurred, or been relevant.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: May 1, 2026, 12:50 a.m.