Triple
T489764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold |
E9958
|
entity |
| Predicate | popularityTrend |
P5318
|
FINISHED |
| Object | peaked in early 20th century in the United States |
—
|
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: peaked in early 20th century in the United States | Statement: [Harold, popularityTrend, peaked in early 20th century in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularityTrend Context triple: [Harold, popularityTrend, peaked in early 20th century in the United States]
-
A.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
B.
peakPopularity
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
-
C.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
D.
popularInPeriod
Indicates that something is widely liked, used, or influential during a specified time period.
-
E.
popularFor
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0e0a9648190b6a3b2da3a3b51e6 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.