Triple
T4875475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannes Stark |
E109192
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Stark |
E149830
|
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: Stark | Statement: [Johannes Stark, familyName, Stark]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stark Context triple: [Johannes Stark, familyName, Stark]
-
A.
Stark
chosen
Stark is a common surname of Scottish origin associated with various notable figures in politics, science, and popular culture.
-
B.
Stange
Stange is a rural municipality in Innlandet county, Norway, known for its agricultural landscape and proximity to the town of Hamar.
-
C.
Stahl
Stahl is a surname of German origin borne by various notable individuals across fields such as sports, politics, and the arts.
-
D.
Steele
Steele is a surname most notably borne by Charles Steele Jr., an American civil rights leader and former president of the Southern Christian Leadership Conference.
-
E.
Steinman
Steinman is a surname most notably associated with David B. Steinman, an influential American civil engineer and bridge designer.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dba3efc8190adcf8b30490b4984 |
completed | March 20, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be67f90e848190a36eee1e670657e4 |
completed | March 21, 2026, 9:42 a.m. |
Created at: March 20, 2026, 1:27 p.m.