Triple
T32653015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Conway, 1st Earl of Conway |
E834786
|
entity |
| Predicate | heldTitleBeforeEarldom |
P175017
|
FINISHED |
| Object | Viscount Conway |
—
|
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: Viscount Conway | Statement: [Edward Conway, 1st Earl of Conway, heldTitleBeforeEarldom, Viscount Conway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldTitleBeforeEarldom Context triple: [Edward Conway, 1st Earl of Conway, heldTitleBeforeEarldom, Viscount Conway]
-
A.
heldEarldom
Indicates that a person possessed and held the noble title and rank of an earl.
-
B.
heldByBeforeDukedom
Indicates that an entity held a particular title, position, or role prior to being granted a dukedom.
-
C.
aristocraticTitleHeldFrom
Indicates the time period or starting point from which an aristocratic title was held by an entity.
-
D.
earldomHeldBy
Indicates that a specified earldom is or was held as a title by a particular person or entity.
-
E.
titleHeldBeforeSuccession
Indicates that an entity held a specific title or position prior to a particular succession event.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1:08 a.m.