Triple
T30061154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Vance |
E763886
|
entity |
| Predicate | hasWritingCharacteristic |
P274
|
FINISHED |
| Object | inventive neologisms |
—
|
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: inventive neologisms | Statement: [Jack Vance, hasWritingCharacteristic, inventive neologisms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWritingCharacteristic Context triple: [Jack Vance, hasWritingCharacteristic, inventive neologisms]
-
A.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
B.
hasWriterCharacter
Indicates that a writer is a character within a work, linking the work to the character who serves as its writer.
-
C.
hasWritingType
Indicates that one entity is associated with, or characterized by, a particular type or form of writing.
-
D.
hasWritingAssociated
Indicates that there is a piece of writing (such as a text, document, or inscription) linked or connected to the given entity.
-
E.
eraCharacteristic
Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given historical or temporal era.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ca34d4081909ea4b2b02523d46a |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:57 p.m.