Triple
T9945461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greg Kroah-Hartman |
E195192
|
entity |
| Predicate | hasHyphenatedSurname |
P37098
|
FINISHED |
| Object | Kroah-Hartman |
E195192
|
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: Kroah-Hartman | Statement: [Greg Kroah-Hartman, hasHyphenatedSurname, Kroah-Hartman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kroah-Hartman Context triple: [Greg Kroah-Hartman, hasHyphenatedSurname, Kroah-Hartman]
-
A.
Kroah-Hartman
chosen
Kroah-Hartman is the hyphenated surname of Greg Kroah-Hartman, a prominent Linux kernel developer and maintainer.
-
B.
Exelmans
Exelmans is a Paris Métro station on Line 9 located in the 16th arrondissement of Paris, France.
-
C.
Klauder
Klauder is a family surname most notably associated with individuals such as physicist John R. Klauder.
-
D.
Parnas
Parnas is a metro station in Saint Petersburg, Russia, serving as the northern terminus of one of the city’s subway lines.
-
E.
Erwin
Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb61561848190aba7250f3b3c4ed5 |
completed | April 2, 2026, 12:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d23d5c6fdc81909b44d0b321201222 |
completed | April 5, 2026, 10:45 a.m. |
Created at: March 30, 2026, 8:45 p.m.