Triple
T16369114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballantyne series |
E397515
|
entity |
| Predicate | protagonistFamilyOrigin |
P123136
|
FINISHED |
| Object | British settlers |
—
|
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: British settlers | Statement: [Ballantyne series, protagonistFamilyOrigin, British settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistFamilyOrigin Context triple: [Ballantyne series, protagonistFamilyOrigin, British settlers]
-
A.
protagonistOrigin
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
-
B.
protagonistFamilyName
Indicates that the subject is the family name (surname) of the story’s protagonist.
-
C.
protagonistBackground
Indicates that one entity serves as the background, history, or prior circumstances of the protagonist entity in a narrative or story.
-
D.
protagonistOriginTime
Indicates the point in time at which the protagonist first comes into existence or begins their story.
-
E.
protagonistFamilyStatus
Indicates the familial role or position that a character holds in relation to the story’s protagonist.
- F. None of above. chosen
Provenance (4 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff4021e88190ad093bab74cf82a4 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.