Triple
T33613428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Porchester |
E861049
|
entity |
| Predicate | associatedWithEarldom |
P142659
|
FINISHED |
| Object | Earl of Carnarvon |
E1507296
|
NE 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: Earl of Carnarvon | Statement: [Lord Porchester, associatedWithEarldom, Earl of Carnarvon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithEarldom Context triple: [Lord Porchester, associatedWithEarldom, Earl of Carnarvon]
-
A.
earldomHeldBy
chosen
Indicates that a specified earldom is or was held as a title by a particular person or entity.
-
B.
holdsOneOfOldestEarldomsIn
Indicates that an entity possesses one of the most ancient or historically earliest-established earldoms within a specified region or jurisdiction.
-
C.
heldEarldom
Indicates that a person possessed and held the noble title and rank of an earl.
-
D.
associatedWithFeudalOffice
Indicates a relationship where an entity is linked to, holds, or is otherwise connected with a specific feudal office or position within a feudal system.
-
E.
associatedWithMonarchy
Indicates a relationship in which something has a connection, link, or relevance to a monarchy or monarchical system.
- F. None of above.
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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a363c81558c8190bc6dd14913506d6b |
completed | June 20, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:41 a.m.