Triple
T17300761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erle P. Halliburton |
E420032
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Erle |
E572513
|
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: Erle | Statement: [Erle P. Halliburton, givenName, Erle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Erle Context triple: [Erle P. Halliburton, givenName, Erle]
-
A.
Erle
chosen
Erle is the given name of Erle Stanley Gardner, the American lawyer and prolific author best known for creating the fictional defense attorney Perry Mason.
-
B.
Elke
Elke is a feminine given name of German origin commonly used in German-speaking countries.
-
C.
Erlich
Erlich is a variant spelling of the surname Ehrlich, which is of German origin and commonly associated with Jewish families.
-
D.
Esselen
Esselen is a nearly extinct Native American language once spoken by the Esselen people of the central California coast.
-
E.
Elpe
Elpe is a river in North Rhine-Westphalia, Germany, known as a tributary of the Lenne in the Sauerland region.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438f9e5ac8190ba0b5820790112d9 |
completed | April 19, 2026, 2:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0180dc929c819096a7a5dc81e5b6ef |
completed | May 11, 2026, 7:10 a.m. |
Created at: April 10, 2026, 5:41 a.m.