Triple
T31557605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oliver |
E805168
|
entity |
| Predicate | wasTopBoysNameInPeriod |
P26902
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [Oliver, wasTopBoysNameInPeriod, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTopBoysNameInPeriod Context triple: [Oliver, wasTopBoysNameInPeriod, 2010s]
-
A.
wasTopGivenNameInCountry
chosen
Indicates that a given name held the highest popularity rank among all given names within a specified country for a particular time period.
-
B.
wasFashionableIn
Indicates that something was considered stylish, popular, or in vogue during a particular time period or era.
-
C.
characterInPeriod
Indicates that a character exists or is active during a specified historical or temporal period.
-
D.
notablePopularityPeriod
Indicates the time span during which something was especially popular or widely recognized.
-
E.
wasNamedInYear
Indicates that an entity received or was given its name in a specific year.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:13 p.m.