Triple
T21887494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADX |
E540443
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Leuchars |
—
|
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: Leuchars | Statement: [ADX, associatedWith, Leuchars]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leuchars Context triple: [ADX, associatedWith, Leuchars]
-
A.
Leuchars
chosen
Leuchars is a village in Fife, Scotland, known for its nearby former RAF base and its railway station serving as a key access point for St Andrews.
-
B.
Rosyth
Rosyth is a Scottish port town on the north shore of the Firth of Forth, known for its naval dockyard and ferry connections.
-
C.
Huntly
Huntly is a historic town in Aberdeenshire, Scotland, long associated with the Gordon family and the Marquess of Huntly.
-
D.
Huntly
Huntly is a small town in New Zealand known for its coal mining history and location on the Waikato River between Hamilton and Auckland.
-
E.
Huntly
Huntly is a small town in Victoria, Australia, situated near Bendigo in the state's central region.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ed35948190bbffba2c40029eee |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 16, 2026, 7:05 p.m.