Triple
T19878606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arenberg family |
E477704
|
entity |
| Predicate | elevationToPrincelyStatus |
P76991
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Arenberg family, elevationToPrincelyStatus, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationToPrincelyStatus Context triple: [Arenberg family, elevationToPrincelyStatus, 17th century]
-
A.
elevatedToPrincipalityBy
Indicates that an entity was raised in status or rank to a principality by another entity or authority.
-
B.
elevatedToDuchy
Indicates that a territory, region, or domain has been formally raised in rank or status to become a duchy.
-
C.
elevatedToArchduchy
Indicates that an entity’s status or rank has been raised to that of an archduchy.
-
D.
gainedPrincelyStatusInCentury
chosen
Indicates that an entity obtained or was elevated to princely rank or status during a specified century.
-
E.
elevatedToKingdomBy
Indicates that one entity raised or promoted another entity to the status or rank of a kingdom.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658dc8ce08190b005ad49924e5659 |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.