Triple
T22238488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Rivers |
E549653
|
entity |
| Predicate | hasSiblingGroupName |
P41040
|
FINISHED |
| Object | Rivers siblings |
—
|
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: Rivers siblings | Statement: [Mary Rivers, hasSiblingGroupName, Rivers siblings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiblingGroupName Context triple: [Mary Rivers, hasSiblingGroupName, Rivers siblings]
-
A.
siblingGroup
chosen
Indicates that multiple individuals belong to the same set of siblings, sharing at least one parent in common.
-
B.
hasSiblingMembers
Indicates that two entities are members of a group or organization and are siblings to each other within that membership context.
-
C.
hasSiblingTier
Indicates that two entities occupy the same or equivalent sibling level or rank within a hierarchical structure.
-
D.
hasSiblingType
Indicates that one entity has another entity as a sibling, specifying the type or category of that sibling relationship.
-
E.
hasRelatedGroup
Indicates that one group or collection is associated with another group or collection through some defined relationship or connection.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132123a048190ba5a90d7acb9aeb2 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.