Triple
T22258491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorden Tallis |
E550154
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Gorden |
—
|
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: Gorden | Statement: [Gorden Tallis, givenName, Gorden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gorden Context triple: [Gorden Tallis, givenName, Gorden]
-
A.
Gorden
chosen
Gorden is a masculine given name, notably borne by former Australian rugby league footballer Gorden Tallis.
-
B.
Gardon
The Gardon is a river in southern France known for flowing through the Gard department and beneath the famous Pont du Gard Roman aqueduct.
-
C.
Gardi
Gardi is the nickname of Ibrahim Khan Gardi, an 18th-century Indian military commander renowned for leading artillery forces in the Third Battle of Panipat.
-
D.
Gordon
Gordon is a residential suburb located within the Brindabella region of the Australian Capital Territory.
-
E.
Gordon
Gordon is a Jewish surname notably borne by the 19th-century Hebrew poet and Enlightenment figure Judah Leib Gordon.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c4bff48190b4be83f5f7677ac8 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 16, 2026, 8:39 p.m.