Triple
T34978193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Believer Book Award |
E1008739
|
entity |
| Predicate | hasLonglist |
P198711
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Believer Book Award, hasLonglist, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLonglist Context triple: [Believer Book Award, hasLonglist, yes]
-
A.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
B.
hasOptionsListed
Indicates that one entity presents or enumerates a set of selectable options associated with another entity or context.
-
C.
hasSpecialList
Indicates that an entity possesses or is associated with a designated special list distinct from regular or default lists.
-
D.
hasLongStretchIn
Indicates that something extends for a considerable or continuous distance within a specified area, medium, or context.
-
E.
listedFor
Indicates that something has been placed on a list or made available in a catalog, registry, or marketplace for consideration, viewing, or potential selection.
- F. None of above. chosen
Provenance (4 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
| PDg | Predicate description generation | batch_69feff703fec8190ab7d0633e0cc5459 |
completed | May 9, 2026, 9:33 a.m. |
Created at: May 3, 2026, 4:01 p.m.