Triple
T18136198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Per Gunnar Hansson |
E434142
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Per |
—
|
NE NERFINISHED |
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: Per | Statement: [Per Gunnar Hansson, givenName, Per]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Per Context triple: [Per Gunnar Hansson, givenName, Per]
-
A.
Per
chosen
Per is a Scandinavian masculine given name, commonly used in Norway, Sweden, and Denmark as a form of Peter.
-
B.
Pe
Pe is a Hebrew consonant letter that represents a "p" or "f" sound and has both standard and final written forms.
-
C.
Par
Par is a shortened variant of the surname "Parr," commonly used as a family name in various cultures.
-
D.
PER
PER is the IATA airport code for Perth Airport, the main international and domestic gateway serving Perth in Western Australia.
-
E.
PER
PER is the FIFA country code used to represent the Peru national football team in international competitions and official records.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de07b4b4819085fe80beb7addfd0 |
completed | April 19, 2026, 1:52 p.m. |
Created at: April 10, 2026, 10:29 a.m.