Triple
T22981106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabel Amberson Minafer |
E571465
|
entity |
| Predicate | characterInEra |
P119878
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Isabel Amberson Minafer, characterInEra, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterInEra Context triple: [Isabel Amberson Minafer, characterInEra, late 19th century]
-
A.
characterInPeriod
chosen
Indicates that a character exists or is active during a specified historical or temporal period.
-
B.
linkedToCharacterEra
Indicates that one entity is associated with, or belongs to, a particular period or era in a character’s timeline or development.
-
C.
characterCreatedInYear
Indicates the specific calendar year in which a fictional or narrative character was first created or introduced.
-
D.
isContemporaryOfFictionalCharacter
Indicates that one entity exists or occurs in the same fictional time period as another fictional character.
-
E.
depictedPersonEra
Indicates the historical era or time period associated with the person depicted in an image or representation.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829589548190863619aebcae026c |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.