Triple
T23508961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwina Brown |
E572362
|
entity |
| Predicate | siblingOrderInFamily |
P20593
|
FINISHED |
| Object | one of the Brown sisters |
—
|
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: one of the Brown sisters | Statement: [Edwina Brown, siblingOrderInFamily, one of the Brown sisters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siblingOrderInFamily Context triple: [Edwina Brown, siblingOrderInFamily, one of the Brown sisters]
-
A.
positionInFamilyBirthOrder
chosen
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
B.
siblingCount
Indicates the number of siblings an entity has.
-
C.
sibling
Indicates that two entities share at least one parent, making them brothers or sisters to each other.
-
D.
siblingOrRelative
Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
-
E.
positionInFamilyTree
Indicates the familial relationship or generational position one person holds relative to another within a family tree.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a902c0788190840d7df1b5450b4d |
completed | April 29, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:07 p.m.