Triple
T19338296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delbert |
E483679
|
entity |
| Predicate | nameUsageTrend |
P5318
|
FINISHED |
| Object | declining in late 20th century |
—
|
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: declining in late 20th century | Statement: [Delbert, nameUsageTrend, declining in late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameUsageTrend Context triple: [Delbert, nameUsageTrend, declining in late 20th century]
-
A.
nameUsedSince
Indicates that a particular name has been in use for an entity starting from a specified point in time.
-
B.
languageUseTrend
Indicates how the use or prevalence of a particular language changes over time within a given population or context.
-
C.
namePopularityType
Indicates the category or type of popularity associated with a given name (e.g., how or in what way the name is considered popular).
-
D.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
E.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185538d48190ae4fa3ac0b0ca182 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.