Triple
T14918922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhine bridge at Arnhem |
E371456
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | John Frost |
E473086
|
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: John Frost | Statement: [Rhine bridge at Arnhem, namedAfter, John Frost]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: John Frost Context triple: [Rhine bridge at Arnhem, namedAfter, John Frost]
-
A.
John Frost
John Frost was a 19th-century Welsh Chartist leader best known for leading the 1839 Newport Rising, one of the most significant armed uprisings in British working-class history.
-
B.
John Frostbrug
chosen
John Frostbrug is a historic road bridge in Arnhem, Netherlands, famously associated with the World War II Battle of Arnhem during Operation Market Garden.
-
C.
James Frost
James Frost is a music video director known for his visually inventive work with artists such as Coldplay and Radiohead.
-
D.
William Frost
William Frost is a relatively obscure historical figure whose name is notably associated with the surname Frost.
-
E.
John Fry
John Fry is a relatively common personal name that may refer to multiple individuals across various professions and contexts.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62f76bc81909ebc8899096cd1a0 |
completed | April 15, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe72c141088190936f2fd53fee80e4 |
completed | May 8, 2026, 11:33 p.m. |
Created at: April 10, 2026, 2:33 a.m.