Triple
T26877793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Ross (jure uxoris, disputed) |
E676801
|
entity |
| Predicate | associatedEarldom |
P142659
|
FINISHED |
| Object | Earldom of Ross |
—
|
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: Earldom of Ross | Statement: [Earl of Ross (jure uxoris, disputed), associatedEarldom, Earldom of Ross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedEarldom Context triple: [Earl of Ross (jure uxoris, disputed), associatedEarldom, Earldom of Ross]
-
A.
earldomHeldBy
chosen
Indicates that a specified earldom is or was held as a title by a particular person or entity.
-
B.
heldEarldom
Indicates that a person possessed and held the noble title and rank of an earl.
-
C.
holdsOneOfOldestEarldomsIn
Indicates that an entity possesses one of the most ancient or historically earliest-established earldoms within a specified region or jurisdiction.
-
D.
earldomExtinct
Indicates that a particular earldom has ceased to exist, typically due to the lack of eligible heirs or formal termination of the title.
-
E.
EarlMarshal
Indicates a person holds the office or role of Earl Marshal in relation to a sovereign, state, or ceremonial hierarchy.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff80d9a1d88190a95b1488acd6e2e5 |
completed | May 9, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69ff802ae2dc819093a3cda42b63dcbd |
completed | May 9, 2026, 6:42 p.m. |
Created at: April 27, 2026, 5:37 a.m.