Triple
T23259990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wendy |
E581976
|
entity |
| Predicate | popularityNote |
P92690
|
FINISHED |
| Object | became popular in the 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: became popular in the 20th century | Statement: [Wendy, popularityNote, became popular in the 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularityNote Context triple: [Wendy, popularityNote, became popular in the 20th century]
-
A.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
B.
popularityContext
Indicates the situational or domain-specific setting in which something’s popularity or level of public favor is evaluated.
-
C.
peakPopularity
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
-
D.
popularFrom
chosen
Indicates that something gains or holds popularity starting from a specific time, source, or context.
-
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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c7ec148190b01fd215a0c1daa1 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:11 p.m.