Triple
T27370540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jill McBain |
E690304
|
entity |
| Predicate | residesInStory |
P98527
|
FINISHED |
| Object | frontier town near Flagstone |
—
|
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: frontier town near Flagstone | Statement: [Jill McBain, residesInStory, frontier town near Flagstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residesInStory Context triple: [Jill McBain, residesInStory, frontier town near Flagstone]
-
A.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
-
B.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
C.
homeLocationInStory
chosen
Indicates the place that serves as a character’s primary home or base of residence within the context of the story.
-
D.
residesInFictionalLocation
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
E.
residesDuringSeries
Indicates that one entity lives or is based in a particular place for the duration of a specified series or sequence of events.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 12:18 p.m.