Triple
T30484507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivian |
E775677
|
entity |
| Predicate | hasUsageInLiterature |
P18520
|
FINISHED |
| Object | English literature |
—
|
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: English literature | Statement: [Vivian, hasUsageInLiterature, English literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUsageInLiterature Context triple: [Vivian, hasUsageInLiterature, English literature]
-
A.
hasHistoriographicalUse
Indicates that something is used or cited within historical writing or analysis as part of constructing, interpreting, or debating historical narratives.
-
B.
hasReputationInLiterature
Indicates that an entity is recognized or regarded in a particular way within literary works or the field of literature.
-
C.
usedInManuscripts
chosen
Indicates that something (such as a term, symbol, or feature) appears or is employed within one or more manuscripts.
-
D.
hasViewOnLiterature
Indicates that an entity holds a particular opinion, perspective, or stance regarding literature.
-
E.
hasLiterarySignificance
Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:13 p.m.