Triple
T32571081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emily Taylor |
E832514
|
entity |
| Predicate | hasAliasInPlot |
P61831
|
FINISHED |
| Object | Emily Taylor (no known alternate name) |
—
|
NE NERFINISHED |
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: Emily Taylor (no known alternate name) | Statement: [Emily Taylor, hasAliasInPlot, Emily Taylor (no known alternate name)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAliasInPlot Context triple: [Emily Taylor, hasAliasInPlot, Emily Taylor (no known alternate name)]
-
A.
hasAliasInNarrative
chosen
Indicates that an entity is referred to by an alternative name or alias within a specific narrative or story context.
-
B.
hasAliasReference
Indicates that one entity serves as an alternate name or alias referring to another entity.
-
C.
usesAliasIn
Indicates that one entity operates under or refers to another entity by an alternative name or alias within a specific context.
-
D.
hasAliasUsedByVincent
Indicates that an alias or alternate name is (or was) used by the person Vincent.
-
E.
isKeyToPlotOf
Indicates that something plays a crucial, defining role in driving or enabling the main events or structure of a plot.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:03 a.m.