Triple
T6232846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long |
E139397
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Lange |
E92052
|
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: Lange | Statement: [Long, hasCognate, Lange]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lange Context triple: [Long, hasCognate, Lange]
-
A.
Lange
chosen
Lange is a German surname borne by numerous notable individuals across fields such as science, politics, arts, and sports.
-
B.
Langer
Langer is a surname most notably associated with Robert Langer, a pioneering American chemical engineer and prolific inventor in biotechnology and drug delivery.
-
C.
Longo
Longo is an Italian surname borne by various notable figures in politics, arts, and sports.
-
D.
Lansen
Lansen is the NATO reporting name for the Swedish Saab 32, a Cold War-era jet aircraft used primarily for attack and reconnaissance roles.
-
E.
Lazgi
Lazgi is a vibrant and expressive traditional Uzbek dance known for its rapid hand movements, lively rhythms, and roots in the cultural heritage of the Khorezm 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062ee6f088190bf72692eb8ffb761 |
completed | March 22, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c20defd338819099a23d00107c4edd |
completed | March 24, 2026, 4:07 a.m. |
Created at: March 22, 2026, 4:22 p.m.