Triple
T15823048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Fleming |
E383659
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Fleming |
E18669
|
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: Fleming | Statement: [Town of Fleming, hasName, Fleming]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fleming Context triple: [Town of Fleming, hasName, Fleming]
-
A.
Fleming
chosen
Fleming is a surname most famously associated with Ian Fleming, the British author who created the James Bond spy novels.
-
B.
Flemming
Flemming is a surname and given name of Germanic origin, used by various notable individuals across fields such as politics, arts, and science.
-
C.
Colhoun
Colhoun is a Scottish surname, historically associated with Clan Colquhoun and its descendants.
-
D.
Líster
Líster is a Spanish surname most notably associated with Enrique Líster, a prominent communist military commander during the Spanish Civil War.
-
E.
Grahame
Grahame is a surname of English and Scottish origin borne by various notable individuals.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a96b848190845cf547034a24f2 |
completed | April 16, 2026, 11:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff999bba548190a39adc2d0e11c605 |
completed | May 9, 2026, 8:31 p.m. |
Created at: April 10, 2026, 4:49 a.m.