Triple
T7703533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drapier's Letters |
E174556
|
entity |
| Predicate | pseudonymousCharacterOccupation |
P34569
|
FINISHED |
| Object | draper |
—
|
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: draper | Statement: [Drapier's Letters, pseudonymousCharacterOccupation, draper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pseudonymousCharacterOccupation Context triple: [Drapier's Letters, pseudonymousCharacterOccupation, draper]
-
A.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
-
B.
namedAfterFictionalCharacter
Indicates that one entity has been given its name in honor of, or derived from, a fictional character.
-
C.
fictionalOccupation
chosen
Indicates that one entity is the imaginary or narrative-based job, role, or profession attributed to another entity within a fictional context.
-
D.
pseudonymInspiredBy
Indicates that a pseudonym was chosen or created based on, or in homage to, another name, person, work, or concept.
-
E.
characterAlias
Indicates that one character is known or referred to by an alternative name or alias.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.