Triple
T12668649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Data |
E302620
|
entity |
| Predicate | "brother" |
P62992
|
FINISHED |
| Object | B-4 |
—
|
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: B-4 | Statement: [Data, "brother", B-4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: "brother" Context triple: [Data, "brother", B-4]
-
A.
sibling
Indicates that two entities share at least one parent, making them brothers or sisters to each other.
-
B.
adoptiveBrother
Indicates that one person is the brother of another through adoption rather than biological relation.
-
C.
fosterBrother
Indicates a sibling relationship where one male is considered a brother to another due to being raised in the same foster family rather than through biological or legal adoption ties.
-
D.
brotherInLaw
Indicates a relationship where one person is the brother of someone's spouse, the spouse of someone's sibling, or the spouse of the sibling of someone's spouse.
-
E.
brotherStatus
chosen
Indicates that one entity has the role or relationship of being a brother in relation to another entity.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.