Triple
T32316929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobbi Anderson |
E825661
|
entity |
| Predicate | residesAtBeginningOfStory |
P21329
|
FINISHED |
| Object | rural property near Haven, Maine |
—
|
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: rural property near Haven, Maine | Statement: [Bobbi Anderson, residesAtBeginningOfStory, rural property near Haven, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residesAtBeginningOfStory Context triple: [Bobbi Anderson, residesAtBeginningOfStory, rural property near Haven, Maine]
-
A.
firstRegularStory
Indicates that an entity is the earliest or primary standard (non-special) story associated with another entity in a sequence or collection.
-
B.
protagonistStatusAtStart
Indicates the role or condition the main character is in at the beginning of the narrative or event.
-
C.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
D.
firstAppearanceStory
Indicates the story in which an entity is depicted or mentioned for the first time.
-
E.
narrativeStart
chosen
Indicates the point or event at which a narrative, story, or sequence of events begins.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 12:46 a.m.