Triple
T25108931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Brother |
E628939
|
entity |
| Predicate | subjectRelationToAuthor |
P157650
|
FINISHED |
| Object | brother |
—
|
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: brother | Statement: [My Brother, subjectRelationToAuthor, brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectRelationToAuthor Context triple: [My Brother, subjectRelationToAuthor, brother]
-
A.
editorRelationshipToAuthors
Indicates the editorial role or connection an editor has in relation to the authors of a work.
-
B.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
C.
hasAuthorRelationshipToSubject
Indicates that an entity serves as the author or creator of the specified subject.
-
D.
authorRelationshipToMainSubject
Indicates the nature of the connection or role the author has in relation to the main subject.
-
E.
relatedToAuthorWork
Indicates that there is a connection or association between an author and a work they have created, contributed to, or are otherwise linked with.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4657448e88190993f7c497f8e808f |
completed | May 1, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:26 a.m.