Triple
T19692313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forbes 30 Under 30 – Media (2012) |
E472863
|
entity |
| Predicate | hasEditionYear |
P92879
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Forbes 30 Under 30 – Media (2012), hasEditionYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEditionYear Context triple: [Forbes 30 Under 30 – Media (2012), hasEditionYear, 2012]
-
A.
mostRecentEditionYear
Indicates the calendar year in which the most recently released edition of an entity (such as a work, product, or publication) was published or made available.
-
B.
hasFirstEditionYear
Indicates the year in which the first edition of an item (such as a work, book, or publication) was originally released or published.
-
C.
correctedEditionYear
Indicates the year in which a corrected or revised edition of a work was published or released.
-
D.
editionPublicationYear
chosen
Indicates the calendar year in which a particular edition of a work was published.
-
E.
notableEditionYear
Indicates the year in which a particular edition of something (such as a work, product, or publication) is considered notable or significant.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64210cddc8190836faa2996a44457 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.