Triple
T5168786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneers (Time 100 category) |
E116622
|
entity |
| Predicate | editorialGenre |
P46396
|
FINISHED |
| Object | listicle |
—
|
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: listicle | Statement: [Pioneers (Time 100 category), editorialGenre, listicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorialGenre Context triple: [Pioneers (Time 100 category), editorialGenre, listicle]
-
A.
publishedGenre
Indicates that an entity has been published in, or is associated with, a particular genre.
-
B.
genre
Indicates the artistic or thematic category to which a work (such as a book, film, or song) belongs.
-
C.
editorialFormat
chosen
Indicates the specific editorial style, layout, or presentation format in which content is produced or published.
-
D.
editorialStandard
Indicates that one entity defines, follows, or enforces a particular set of editorial rules, guidelines, or quality criteria in relation to another entity or content.
-
E.
editorialRole
Indicates that one entity holds an editorial position or responsibility in relation to another entity, such as a publication, work, or organization.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd794dd9988190922e138f2a9a3c62 |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.