Triple
T10782074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pollyanna Whittier |
E254344
|
entity |
| Predicate | fictionalOrphanStatus |
P95446
|
FINISHED |
| Object | orphan |
—
|
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: orphan | Statement: [Pollyanna Whittier, fictionalOrphanStatus, orphan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalOrphanStatus Context triple: [Pollyanna Whittier, fictionalOrphanStatus, orphan]
-
A.
fictionalStatus
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
-
B.
fictionalBirthStatus
Indicates the relationship between an entity and its status of being born or created within a fictional or imaginary context.
-
C.
fictionalMaritalStatus
Indicates that an entity has a marital status that exists only within a fictional, narrative, or hypothetical context rather than in real life.
-
D.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
E.
hasChildInFiction
Indicates that a fictional work or character includes another character as their child within the fictional narrative.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732c5618081908f72838ed42ed05c |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:17 p.m.