Triple
T21314813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reuss-Greiz |
E525436
|
entity |
| Predicate | hasRulerNamingCustom |
P143695
|
FINISHED |
| Object | all male members named Heinrich (Henry) |
—
|
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 named Heinrich (Henry) | Statement: [Reuss-Greiz, hasRulerNamingCustom, all male members named Heinrich (Henry)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulerNamingCustom Context triple: [Reuss-Greiz, hasRulerNamingCustom, all male members named Heinrich (Henry)]
-
A.
hasRulerCharacter
Indicates that a ruler possesses a particular character trait or quality.
-
B.
hasRulerTitle
Indicates that a ruler holds or is associated with a specific formal title of rulership.
-
C.
hasRuleName
Indicates that an entity is associated with a specific rule identified by a particular name.
-
D.
hasAliasForRuler
Indicates that one name, title, or designation is used as an alternative alias for a specific ruler.
-
E.
recognizedAsRuler
Indicates that one entity is acknowledged or accepted by others as the legitimate ruler or sovereign authority.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dce6b4081909841ac0440fca5e4 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:28 p.m.