Triple
T15493345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peni Parker |
E378750
|
entity |
| Predicate | parentalPredecessor |
P80614
|
FINISHED |
| Object | original SP//dr pilot |
—
|
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: original SP//dr pilot | Statement: [Peni Parker, parentalPredecessor, original SP//dr pilot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalPredecessor Context triple: [Peni Parker, parentalPredecessor, original SP//dr pilot]
-
A.
predecessorFamily
Indicates that one family is the earlier or ancestral family from which another family descends or follows.
-
B.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
predecessorRelationship
chosen
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
-
D.
predecessorStatus
Indicates that one entity’s status is determined by, or directly follows from, the status of a preceding entity in a sequence or process.
-
E.
predecessorProject
Indicates that one project temporally or logically comes before and leads into another project in a sequence or dependency chain.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fad723481908d2aa33e8f065f2f |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:49 a.m.