Triple
T20373142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strength to Endure |
E497123
|
entity |
| Predicate | performedInEra |
P65426
|
FINISHED |
| Object | early 1990s |
—
|
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 1990s | Statement: [Strength to Endure, performedInEra, early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedInEra Context triple: [Strength to Endure, performedInEra, early 1990s]
-
A.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
B.
playedWithEra
chosen
Indicates that an entity performed or was active during a specified historical or stylistic era.
-
C.
associatedProductionEra
Indicates a relationship where something is linked to the specific time period or era during which it was produced or created.
-
D.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
E.
usedDuringEraOf
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678aad7b08190a710a75d6828b21e |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:27 a.m.