Triple
T3406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Person of the Year |
E63
|
entity |
| Predicate | hasEdition |
P35
|
FINISHED |
| Object | special year-end issue |
—
|
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: special year-end issue | Statement: [Time Person of the Year, hasEdition, special year-end issue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEdition Context triple: [Time Person of the Year, hasEdition, special year-end issue]
-
A.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
B.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
C.
hasLegacy
Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
-
D.
hasPart
chosen
Indicates that one entity is a component, segment, or constituent part of another entity.
-
E.
countryOfPublication
Indicates the country in which a work was formally published or made publicly available.
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23bcc8eb48190b897cc331563980a |
completed | Feb. 28, 2026, 12:50 a.m. |
| PD | Predicate disambiguation | batch_69a23994309081909ff3e869deef2156 |
completed | Feb. 28, 2026, 12:40 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.