Triple
T7869828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plymouth Argyle F.C. |
E182709
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Plymouth |
E36964
|
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: Plymouth | Statement: [Plymouth Argyle F.C., city, Plymouth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Plymouth Context triple: [Plymouth Argyle F.C., city, Plymouth]
-
A.
Plymouth
Plymouth is a historic coastal town in Massachusetts, United States, best known as the landing site of the Pilgrims and often called "America’s Hometown."
-
B.
Plymouth
Plymouth is the former capital of Montserrat that was destroyed and permanently evacuated following devastating volcanic eruptions in the 1990s.
-
C.
Plymouth
Plymouth was the original name of the city now known as St. Helens in Columbia County, Oregon.
-
D.
Plymouth
Plymouth is a suburban city in Minnesota known for its residential communities, parks, and proximity to Minneapolis.
-
E.
Plymouth
chosen
Plymouth is a historic port city on the south coast of Devon, England, known for its maritime heritage and role as a major naval base.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3848d6d88190830afcf04ad12154 |
completed | March 31, 2026, 2:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cbdf844f24819091cb8757d29a4a3f |
completed | March 31, 2026, 2:51 p.m. |
Created at: March 30, 2026, 4:55 p.m.