Triple
T30612377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piper Halliwell |
E779211
|
entity |
| Predicate | laterPositionInFamily |
P128953
|
FINISHED |
| Object | eldest sister |
—
|
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: eldest sister | Statement: [Piper Halliwell, laterPositionInFamily, eldest sister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPositionInFamily Context triple: [Piper Halliwell, laterPositionInFamily, eldest sister]
-
A.
positionInFamilyTree
chosen
Indicates the familial relationship or generational position one person holds relative to another within a family tree.
-
B.
previousSubfamilyPlacement
Indicates that an entity was formerly assigned to a different subfamily before its current taxonomic placement.
-
C.
parentOfPosition
Indicates that one position or role is hierarchically above and directly responsible for another position or role.
-
D.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
E.
parentPosition
Indicates that one entity occupies the role of a parent or higher-level position relative to another entity in a hierarchical structure.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: April 29, 2026, 8:26 p.m.