Triple
T13443075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustaf Larson |
E320413
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Larson |
E768962
|
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: Larson | Statement: [Gustaf Larson, familyName, Larson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Larson Context triple: [Gustaf Larson, familyName, Larson]
-
A.
Larson
chosen
Larson is a common surname of Scandinavian origin, meaning "son of Lars."
-
B.
Larsson
Larsson is a common Swedish surname borne by numerous notable individuals across fields such as literature, music, and sports.
-
C.
Lar
Lar is a historic city in Iran’s Fars Province, known for its traditional architecture and role as a regional commercial center.
-
D.
Lorens
Lorens is a character from Paulo Coelho’s novel "Brida," serving as one of the key figures in the protagonist’s spiritual and personal journey.
-
E.
Laird
Laird is a given name of Scottish origin traditionally used as a masculine middle or first name, associated with landownership and nobility.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee881888190811ddf01bc699864 |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f739965ef081909e85881ce805bbb5 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 9, 2026, 9:40 p.m.