Triple
T28586619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plympton |
E723521
|
entity |
| Predicate | wasBorough |
P160211
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Plympton, wasBorough, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBorough Context triple: [Plympton, wasBorough, yes]
-
A.
wasBoroughOf
chosen
Indicates that one place previously held the administrative or territorial status of a borough within another jurisdiction.
-
B.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
C.
isCentralBoroughOf
Indicates that a borough serves as the primary or central administrative or geographic district of a specified city or region.
-
D.
isBoroughSeatOf
Indicates that a place serves as the administrative center or seat of government for a specific borough.
-
E.
otherBoroughs
Indicates that two locations are in different boroughs within the same city or metropolitan area.
- F. None of above.
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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650faaa6481909c631878bda4d1eb |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:18 a.m.