Triple
T26079429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George FitzRoy |
E657789
|
entity |
| Predicate | elevatedToPeerageBy |
P154954
|
FINISHED |
| Object | Charles II of England |
—
|
NE NERFINISHED |
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: Charles II of England | Statement: [George FitzRoy, elevatedToPeerageBy, Charles II of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToPeerageBy Context triple: [George FitzRoy, elevatedToPeerageBy, Charles II of England]
-
A.
elevatedToPeerageFor
Indicates that a person was granted a noble title or peerage specifically as a result of, or in recognition for, a particular reason, action, or service.
-
B.
elevatedToMarquessate
Indicates that an individual or title has been formally raised in rank to the status of a marquessate.
-
C.
elevatedToDukedom
Indicates that an entity has been raised or promoted to the rank or title of a dukedom.
-
D.
dateOfElevationToPeerage
Indicates the specific date on which an individual was formally elevated to a rank of nobility or peerage.
-
E.
nobleTitleGranted
chosen
Indicates that a noble title has been formally conferred upon an entity by an authorized grantor or authority.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 7:37 p.m.