Triple
T12235410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A592 road |
E291576
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Aira Force |
E124011
|
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: Aira Force | Statement: [A592 road, passesNear, Aira Force]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aira Force Context triple: [A592 road, passesNear, Aira Force]
-
A.
Aira Force
chosen
Aira Force is a picturesque waterfall in England’s Lake District, renowned for its dramatic cascades, woodland trails, and stone arch bridge.
-
B.
Airok
Airok is a small settlement located on Ailinglaplap Atoll in the Marshall Islands.
-
C.
Matsukaze
Matsukaze is a classic Noh play, traditionally attributed to Zeami, that poignantly depicts the lingering spirits of two salt-making sisters yearning for their lost lover.
-
D.
Matsuda Force
Matsuda Force is a Japanese military unit featured as an opposing force in the strategy video game "Operation Backhander."
-
E.
Tokyo Apache
Tokyo Apache was a professional basketball team based in Tokyo, Japan that competed in the bj league.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cb2892c81909a97b3ad6ec2c21b |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60ab19a4c8190b4692d7ab0d02a12 |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:51 p.m.