Triple
T26434563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Caithness |
E664603
|
entity |
| Predicate | firstHolderAlsoHeldTitle |
P54528
|
FINISHED |
| Object | Earl of Orkney |
—
|
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: Earl of Orkney | Statement: [Earl of Caithness, firstHolderAlsoHeldTitle, Earl of Orkney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHolderAlsoHeldTitle Context triple: [Earl of Caithness, firstHolderAlsoHeldTitle, Earl of Orkney]
-
A.
alsoHeldByFirstHolder
chosen
Indicates that something possessed or held by a second holder is (or was) also possessed or held by the first holder.
-
B.
firstOwnerTitle
Indicates the title or designation held by the original or earliest owner in the ownership history of an entity.
-
C.
heldTitleAlongWith
Indicates that two or more entities simultaneously held the same title or position during an overlapping period.
-
D.
heldTitleInHerOwnRight
Indicates that a woman personally possessed and exercised a title or rank independently, rather than deriving it through a spouse or male relative.
-
E.
first_holder
Indicates that the subject is the earliest or original holder or possessor of the specified object, title, or right.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: April 26, 2026, 11:52 p.m.