Triple
T17051718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HYMS |
E413712
|
entity |
| Predicate | campus |
P269
|
FINISHED |
| Object | Hull |
E18246
|
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: Hull | Statement: [HYMS, campus, Hull]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hull Context triple: [HYMS, campus, Hull]
-
A.
Hull
Hull is a small coastal town in eastern Massachusetts known for its beaches and seaside community on a narrow peninsula.
-
B.
Hull
Hull is a former city in western Quebec, Canada, that once stood on the north shore of the Ottawa River and is now part of the amalgamated city of Gatineau.
-
C.
Hull
Hull is a common English surname borne by various notable individuals across politics, sports, and the arts.
-
D.
Hull
chosen
Hull, formally known as Kingston upon Hull, is a port city in East Yorkshire, England, noted for its maritime heritage and role as a major North Sea trading hub.
-
E.
Hartlepool
Hartlepool is a coastal town in County Durham, England, known historically for its shipbuilding and maritime heritage.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa26e84819098b41ae15618e813 |
completed | April 18, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ed60d3481909c8144bcb01316a1 |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:34 a.m.