Triple
T16805519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N271 road |
E408470
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Mook |
E488053
|
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: Mook | Statement: [N271 road, connects, Mook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mook Context triple: [N271 road, connects, Mook]
-
A.
Mook
chosen
Mook is a village in the Dutch province of Limburg, known for its scenic location along the Maas River near the German border.
-
B.
Mook
Mook is a surname most notably associated with Robby Mook, an American political strategist and campaign manager.
-
C.
Muno
Muno is a village in the municipality of Florenville in the Wallonia region of southern Belgium.
-
D.
Moqorro
Moqorro is a red priest of R’hllor from the *A Song of Ice and Fire* series, known for his prophetic visions and service to the Lord of Light.
-
E.
Mooz-lum
Mooz-lum is a 2010 independent drama film that explores the experiences of a young Muslim American man struggling with identity and faith in the post-9/11 United States.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cc25dc81909443b2c83155267a |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00b28d3a808190bc94a4f09a10da7e |
completed | May 10, 2026, 4:30 p.m. |
Created at: April 10, 2026, 5:22 a.m.