Triple
T36836866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Christophe |
E910293
|
entity |
| Predicate | createdHereditaryNobility |
P200909
|
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: [House of Christophe, createdHereditaryNobility, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdHereditaryNobility Context triple: [House of Christophe, createdHereditaryNobility, true]
-
A.
aristocraticTitleCreatedFrom
Indicates that an aristocratic title originates from, or was formally established based on, another specified source title or entity.
-
B.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
C.
aristocraticTitleCreatedBy
Indicates that an aristocratic title was formally established or instituted by a specific person or authority.
-
D.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
E.
nobleTitleGranted
Indicates that a noble title has been formally conferred upon an entity by an authorized grantor or 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb82be8148190a1c870d467a28c80 |
completed | May 9, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69ffb7bbd550819094052e9a0d0ae320 |
completed | May 9, 2026, 10:39 p.m. |
| PDg | Predicate description generation | batch_69ffb82b40788190bf401344a3f288dd |
completed | May 9, 2026, 10:41 p.m. |
Created at: May 3, 2026, 4:13 p.m.