Triple
T17142652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Lauderdale |
E416005
|
entity |
| Predicate | nobleRank |
P914
|
FINISHED |
| Object | Earl |
E15423
|
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 | Statement: [Earl of Lauderdale, nobleRank, Earl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Earl Context triple: [Earl of Lauderdale, nobleRank, Earl]
-
A.
Earl
chosen
An Earl is a noble rank in the British and some European peerage systems, historically positioned below a marquess and above a viscount.
-
B.
Earl
Earl is one of the two laid-back alien protagonists from the funky, comedic video game series "ToeJam & Earl."
-
C.
Earl
Earl is a masculine given name of English origin, historically associated with nobility and often used in the United States.
-
D.
Earle
Earle is the middle name of Gordon E. Moore, the co-founder of Intel and originator of Moore’s Law.
-
E.
Earle
Earle is a surname most notably associated with Eyvind Earle, the American artist and illustrator renowned for his distinctive background styling in Disney animated films.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d5de10819090cbd65661b018d3 |
completed | April 18, 2026, 9:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01415718c88190834fedae7b01ac69 |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 10, 2026, 5:36 a.m.