Triple
T8761726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans-Jürgen |
E208215
|
entity |
| Predicate | nameOrder |
P20511
|
FINISHED |
| Object | Hans precedes Jürgen |
E208215
|
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: Hans precedes Jürgen | Statement: [Hans-Jürgen, nameOrder, Hans precedes Jürgen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hans precedes Jürgen Context triple: [Hans-Jürgen, nameOrder, Hans precedes Jürgen]
-
A.
HANS
HANS is the radio callsign used by Lufthansa CityLine, a regional airline within the Lufthansa Group.
-
B.
Hans
Hans is a masculine given name of Germanic origin commonly used in Germanic and Scandinavian countries.
-
C.
Hansi
Hansi is a historic town in the Hisar district of Haryana, India, known for its ancient forts and archaeological significance.
-
D.
Hans-Jürgen
chosen
Hans-Jürgen is a masculine German given name, typically used as a compound first name combining "Hans" and "Jürgen."
-
E.
Jürgen
Jürgen is a masculine given name of German origin, commonly used in German-speaking countries.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dfa9d6c81908c4c6b3a6f84f67d |
completed | March 31, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf4354a4c081908c338db408694abf |
completed | April 3, 2026, 4:34 a.m. |
Created at: March 30, 2026, 6:40 p.m.