Triple
T6999808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent of the Kingdom of Hungary |
E162305
|
entity |
| Predicate | wasNonHereditary |
P36963
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Regent of the Kingdom of Hungary, wasNonHereditary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasNonHereditary Context triple: [Regent of the Kingdom of Hungary, wasNonHereditary, true]
-
A.
nonHereditary
chosen
Indicates that a trait, condition, or status is not passed down genetically from parents to offspring.
-
B.
notPrimaryHeir
Indicates that the referenced person is explicitly not the main or principal heir in an inheritance or succession context.
-
C.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
D.
hereditaryButNotNobleRank
Indicates that an entity holds a rank or title that is inherited across generations but does not confer noble status.
-
E.
hasNotableLineage
Indicates that an entity descends from, or is associated with, a distinguished or historically significant family, ancestry, or heritage.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc0e54c88190b092870f2d128510 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.