Triple
T20542368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vernie |
E504371
|
entity |
| Predicate | notabilityInWork |
P51773
|
FINISHED |
| Object | notablePartOfStoryOrStructure |
—
|
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: notablePartOfStoryOrStructure | Statement: [Vernie, notabilityInWork, notablePartOfStoryOrStructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notabilityInWork Context triple: [Vernie, notabilityInWork, notablePartOfStoryOrStructure]
-
A.
notabilityScope
Indicates the domain, field, or context within which something is considered notable or significant.
-
B.
notabilityReason
chosen
Indicates the specific cause, basis, or context for which an entity is considered notable or significant.
-
C.
notableFromWork
Indicates that an entity is notable or well-known specifically because of a particular work it created, contributed to, or is associated with.
-
D.
notabilityStatus
Indicates whether and how an entity is recognized as notable or significant within a given context or system.
-
E.
notableWorkUsed
Indicates that a particular notable work is utilized, referenced, or incorporated in relation to another entity or context.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a292dd1c8190b5c3031f3b44eb52 |
completed | April 20, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.