Triple
T10115699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan |
E218350
|
entity |
| Predicate | hasShortForm |
P43
|
FINISHED |
| Object | Loge |
E804186
|
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: Loge | Statement: [Logan, hasShortForm, Loge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Loge Context triple: [Logan, hasShortForm, Loge]
-
A.
Loge
chosen
Loge is the cunning demigod of fire in Wagner’s Ring cycle, serving as a wily mediator and trickster among gods and mortals.
-
B.
Leyhof
Leyhof is a residential neighborhood in the Dutch town of Leiderdorp, located in the province of South Holland.
-
C.
Noghere
Noghere is a locality within the municipality of Muggia in northeastern Italy, near the Gulf of Trieste.
-
D.
Loganlea
Loganlea is a small settlement in West Lothian, Scotland, situated near Addiewell and served by the nearby Addiewell railway station.
-
E.
Lothagam
Lothagam is an archaeological and geological site in northern Kenya known for its ancient human burials and prominent rock formations along the western shore of Lake Turkana.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd161831c81908bb3c77caa7c3ce1 |
completed | April 2, 2026, 2:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2cc2b00488190acca51a797beed45 |
completed | April 5, 2026, 8:55 p.m. |
Created at: March 30, 2026, 9:04 p.m.