Triple
T4753594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adolf |
E105533
|
entity |
| Predicate | currentPopularity |
P1755
|
FINISHED |
| Object | has strongly declined in use |
—
|
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: has strongly declined in use | Statement: [Adolf, currentPopularity, has strongly declined in use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentPopularity Context triple: [Adolf, currentPopularity, has strongly declined in use]
-
A.
popularityContext
Indicates the situational or domain-specific setting in which something’s popularity or level of public favor is evaluated.
-
B.
peakPopularity
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
-
C.
popularity
chosen
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
D.
popularInPeriod
Indicates that something is widely liked, used, or influential during a specified time period.
-
E.
cultPopularFrom
Indicates that something has gained or exhibits cult popularity originating from a particular source, context, or group.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64e72d1c81908eb60960751e52b1 |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.