Triple
T3320553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Beaconsfield |
E69784
|
entity |
| Predicate | rank |
P268
|
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 Beaconsfield, rank, earl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: earl Context triple: [Earl of Beaconsfield, rank, 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.
Earle
Earle is the middle name of Gordon E. Moore, the co-founder of Intel and originator of Moore’s Law.
-
C.
Earl the Pearl
Earl the Pearl is the Hall of Fame NBA guard Earl Monroe, renowned for his flashy, creative scoring and pivotal role with the Baltimore Bullets and New York Knicks in the 1960s and 1970s.
-
D.
El
El is the common nickname for Philadelphia’s elevated Market–Frankford rapid transit line operated by SEPTA.
-
E.
El
El is the chief god of the ancient Canaanite pantheon, often depicted as a patriarchal creator and father of other deities.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13b85208190b13aba355d5dafcf |
completed | March 8, 2026, 5:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b31a776f3881908e8b198f31921453 |
completed | March 12, 2026, 7:56 p.m. |
Created at: March 8, 2026, 3:11 p.m.