Triple
T35155263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulick Burke, 1st Marquess of Clanricarde |
E1015101
|
entity |
| Predicate | createdMarquessate |
P117760
|
FINISHED |
| Object | 1646 |
—
|
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: 1646 | Statement: [Ulick Burke, 1st Marquess of Clanricarde, createdMarquessate, 1646]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdMarquessate Context triple: [Ulick Burke, 1st Marquess of Clanricarde, createdMarquessate, 1646]
-
A.
createdMarquess
Indicates that one entity formally established or granted the noble title of marquess to another entity.
-
B.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
C.
elevatedToMarquessate
chosen
Indicates that an individual or title has been formally raised in rank to the status of a marquessate.
-
D.
dateOfCreationAsMarquess
Indicates the specific date on which a person was created or elevated to the rank or title of marquess.
-
E.
succeededByInMarquessate
Indicates that one entity was the immediate successor of another in holding a particular marquessate title.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:02 p.m.