Triple
T35310042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Younger Brother, Younger Son |
E1019743
|
entity |
| Predicate | hasAuthorBrother |
P193855
|
FINISHED |
| Object | Alan Clark |
—
|
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: Alan Clark | Statement: [Younger Brother, Younger Son, hasAuthorBrother, Alan Clark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorBrother Context triple: [Younger Brother, Younger Son, hasAuthorBrother, Alan Clark]
-
A.
hasBrothers
Indicates that a person has one or more male siblings.
-
B.
hasNumberOfBrothers
Indicates that an entity is associated with a specific count representing how many brothers it has.
-
C.
hasHalfBrother
Indicates that one person has a male sibling with whom they share exactly one biological parent.
-
D.
hasBrotherCharacter
Indicates that one character has another character who is their brother.
-
E.
possibleBrother
Indicates a relationship where one entity may be the brother of another, but this has not been confirmed as certain.
- F. None of above. chosen
Provenance (4 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: May 3, 2026, 4:03 p.m.