Triple
T11704520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persson |
E278204
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Petersson |
E278204
|
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: Petersson | Statement: [Persson, hasCognate, Petersson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petersson Context triple: [Persson, hasCognate, Petersson]
-
A.
Persson
chosen
Persson is a common Swedish surname borne by numerous notable individuals in fields such as politics, sports, and entertainment.
-
B.
Pehr
Pehr is a masculine given name of Scandinavian origin, notably borne by Finnish statesman P. E. Svinhufvud.
-
C.
Tom Petersson
Tom Petersson is an American bassist best known as the co-founder and innovative 12-string bass player of the rock band Cheap Trick.
-
D.
Petersen
Petersen is a German surname borne by numerous notable individuals across fields such as film, sports, and politics.
-
E.
Petter
Petter is a masculine given name commonly used in Scandinavian countries, equivalent to the English name Peter.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49c8c38819083d83f5fdec52b7f |
completed | April 10, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef83525ae081909ee6f3fbb5d37dd7 |
completed | April 27, 2026, 3:40 p.m. |
Created at: April 8, 2026, 9:40 p.m.