Triple
T15350351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hundred of Salford |
E367033
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Sale |
E67553
|
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: Sale | Statement: [Hundred of Salford, contains, Sale]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sale Context triple: [Hundred of Salford, contains, Sale]
-
A.
Sale
chosen
Sale is a town in Greater Manchester, England, known as a residential suburb within the Metropolitan Borough of Trafford.
-
B.
Venta
Venta is a major river in the Baltic region that flows through western Latvia and Lithuania before emptying into the Baltic Sea.
-
C.
Sellin
Sellin is a seaside resort town on the German island of Rügen, known for its historic pier and Baltic Sea beaches.
-
D.
Book of Sales
Book of Sales is a classical Islamic jurisprudential text section that details the legal rulings and principles governing commercial transactions and trade.
-
E.
Deal
Deal is a historic coastal town and former fishing and mining port in the county of Kent in southeast England, known for its pier, maritime heritage, and role in coastal defense.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e290efc8190b22c95dcd3e5f57f |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01fd53688190939787a3d6ff3bb9 |
completed | May 9, 2026, 9:44 a.m. |
Created at: April 10, 2026, 3:17 a.m.