Triple
T12694311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan Regional Medical Center |
E303289
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Logan |
E483284
|
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: Logan | Statement: [Logan Regional Medical Center, city, Logan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Logan Context triple: [Logan Regional Medical Center, city, Logan]
-
A.
Logan
Logan is a small village in eastern New Mexico, United States, known for its proximity to Ute Lake and its role as a local recreational and service hub in Quay County.
-
B.
Logan
Logan is a neighborhood in Wyoming, Ohio, that serves as the community surrounding the Wyoming train station.
-
C.
Logan
chosen
Logan is a city in northern Utah known for being home to Utah State University and for its scenic Cache Valley setting.
-
D.
Logan
Logan is a small village located within the council area of East Ayrshire in southwest Scotland.
-
E.
Logan
Logan is a residential neighborhood in North Philadelphia, Pennsylvania, known for its rowhouses and proximity to institutions like La Salle University.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ebd17081909f983567e4b36533 |
completed | April 10, 2026, 8:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f67c7c4c608190a1786accf8d86141 |
completed | May 2, 2026, 10:36 p.m. |
Created at: April 9, 2026, 5:22 p.m.