Triple
T8336279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Earle |
E195794
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Earle |
E34772
|
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: Earle | Statement: [Steve Earle, familyName, Earle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Earle Context triple: [Steve Earle, familyName, Earle]
-
A.
Earle
chosen
Earle is the middle name of Gordon E. Moore, the co-founder of Intel and originator of Moore’s Law.
-
B.
Earl
An Earl is a noble rank in the British and some European peerage systems, historically positioned below a marquess and above a viscount.
-
C.
Eaker
Eaker is a surname most notably associated with U.S. Army Air Forces General Ira C. Eaker, a key air power leader during World War II.
-
D.
Everette
Everette is the given first name of E. Howard Hunt, the American intelligence officer and author involved in the Watergate scandal.
-
E.
Irvin
Irvin is a surname most prominently associated with former NFL wide receiver and sports commentator Michael Irvin.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fd3fc80819097b326119107ad4d |
completed | March 31, 2026, 8:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd95e17300819090e405c4c60b280d |
completed | April 1, 2026, 10:02 p.m. |
Created at: March 30, 2026, 5:57 p.m.