Triple
T24689984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reuss |
E611406
|
entity |
| Predicate | notableMemberNamingCustom |
P160880
|
FINISHED |
| Object | all male members traditionally named Heinrich |
—
|
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: all male members traditionally named Heinrich | Statement: [Reuss, notableMemberNamingCustom, all male members traditionally named Heinrich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMemberNamingCustom Context triple: [Reuss, notableMemberNamingCustom, all male members traditionally named Heinrich]
-
A.
notableMemberCommonName
Indicates that the object is the commonly used or well-known name of a notable member associated with the subject.
-
B.
notableMemberVariant
Indicates that an entity is a specific variant or version of a notable member within a group, class, or category.
-
C.
namedMember
Indicates that an entity is a member of a group, organization, or collection and is identified by a specific name within that membership context.
-
D.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
E.
notableMemberBirthName
Indicates the birth name of a notable member associated with an entity.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f60cd7b3e88190a1206958c0f0b225 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60c32ce088190a620eb59d2499fa9 |
completed | May 2, 2026, 2:37 p.m. |
Created at: April 18, 2026, 3:20 a.m.