Triple
T21119020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elrey Borge Jeppesen |
E520375
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Jepp |
—
|
NE NERFINISHED |
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: Jepp | Statement: [Elrey Borge Jeppesen, nickname, Jepp]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jepp Context triple: [Elrey Borge Jeppesen, nickname, Jepp]
-
A.
Jepp
chosen
Jepp is the nickname of Elrey Borge Jeppesen, an American aviation pioneer best known for creating the first standardized aeronautical navigation charts used worldwide.
-
B.
Jep
Jep is a masculine given name, often used as a short form or variant of names like Jepsen or Jeppe in Scandinavian contexts.
-
C.
Jeffe
Jeffe is an alternative spelling variant of the given name Jeff, typically used as a personal name.
-
D.
JEFF
JEFF is the station code used by SEPTA for Jefferson Station, a major regional rail hub in Center City Philadelphia.
-
E.
Jeppe
Jeppe is a Scandinavian masculine given name, commonly used in Denmark and related to names like Jepser or Jepsen.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7223176c48190bfbaea41c2209a15 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 2:55 p.m.