Triple
T27219052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meg Richardson |
E681217
|
entity |
| Predicate | characterScope |
P51828
|
FINISHED |
| Object | series regular |
—
|
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: series regular | Statement: [Meg Richardson, characterScope, series regular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterScope Context triple: [Meg Richardson, characterScope, series regular]
-
A.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
-
B.
scopeCharacterization
chosen
Indicates how the extent, boundaries, or coverage of something is defined, described, or qualified in relation to another entity or context.
-
C.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
D.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
E.
ownerCharacterization
Indicates how an owner is characterized or described in relation to the entity they own.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 27, 2026, 9:42 a.m.