Triple
T30400755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Prudhoe |
E773339
|
entity |
| Predicate | heldByBeforeDukedom |
P169163
|
FINISHED |
| Object | Algernon Percy |
—
|
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: Algernon Percy | Statement: [Baron Prudhoe, heldByBeforeDukedom, Algernon Percy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByBeforeDukedom Context triple: [Baron Prudhoe, heldByBeforeDukedom, Algernon Percy]
-
A.
heldByBeforeKingship
Indicates that an office, role, or position was held by a person prior to that person attaining kingship.
-
B.
holdsPremierDukedom
Indicates that an entity holds the highest-ranking or most senior dukedom within a given nobility system.
-
C.
heldByHeirApparentOf
Indicates that something is possessed, controlled, or occupied by the heir apparent of a particular person, title, or position.
-
D.
heldEarldom
Indicates that a person possessed and held the noble title and rank of an earl.
-
E.
wasDukeOf
Indicates that a person held the hereditary noble title and ruling position of duke over a specified territory or domain.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68617d5e88190bc09d1ee6437d240 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:03 p.m.