Triple
T1047996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carrie |
E22626
|
entity |
| Predicate | followsInCanon |
P24016
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Carrie, followsInCanon, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsInCanon Context triple: [Carrie, followsInCanon, none]
-
A.
notInCanonOf
Indicates that something is excluded from, or does not belong to, the officially recognized canon of a given work or universe.
-
B.
inCanonOf
Indicates that one entity is officially recognized as part of the established canon or authoritative body of works associated with another entity.
-
C.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
-
D.
followsInText
Indicates that one textual element appears immediately or subsequently after another within the same text.
-
E.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.