Triple
T24305262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twistleton |
E612515
|
entity |
| Predicate | hasFamilyRoleInStories |
P42552
|
FINISHED |
| Object | aristocratic family name |
—
|
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: aristocratic family name | Statement: [Twistleton, hasFamilyRoleInStories, aristocratic family name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyRoleInStories Context triple: [Twistleton, hasFamilyRoleInStories, aristocratic family name]
-
A.
hasSiblingInStory
Indicates that one character in a narrative has at least one sibling who also appears within the same story.
-
B.
hasStaffTypeInStory
Indicates that a story involves or is associated with a particular type or category of staff.
-
C.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
D.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
E.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922641bc81908fa3595941e60741 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:30 a.m.