Triple
T33185966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashlie Walker |
E849468
|
entity |
| Predicate | has sibling |
P363
|
FINISHED |
| Object | Caleb Walker |
—
|
NE NERFINISHED |
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: Caleb Walker | Statement: [Ashlie Walker, has sibling, Caleb Walker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has sibling Context triple: [Ashlie Walker, has sibling, Caleb Walker]
-
A.
hasSiblingMembers
Indicates that two entities are members of a group or organization and are siblings to each other within that membership context.
-
B.
hadSibling
Indicates that one entity and another entity share at least one parent, i.e., they are siblings.
-
C.
hasHalfSibling
Indicates that two individuals share exactly one biological parent in common, making them half-siblings.
-
D.
sibling
chosen
Indicates that two entities share at least one parent, making them brothers or sisters to each other.
-
E.
hasSiblingType
Indicates that one entity has another entity as a sibling, specifying the type or category of that sibling relationship.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:29 a.m.