Triple
T14733951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pembroke River |
E346151
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Pembroke |
E325021
|
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: Pembroke | Statement: [Pembroke River, flowsThrough, Pembroke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pembroke Context triple: [Pembroke River, flowsThrough, Pembroke]
-
A.
Pembroke
Pembroke is a historic town in southwest Wales best known as the birthplace of King Henry VII of England and for its prominent medieval castle.
-
B.
Pembroke
Pembroke is a small city in southeastern Georgia that serves as the administrative and governmental center of Bryan County.
-
C.
Pembroke
Pembroke is a suburban town in southeastern Massachusetts known for its residential character, ponds, and historic New England charm.
-
D.
Pembroke
Pembroke is a small rural city located in Christian County in southwestern Kentucky, United States.
-
E.
Pembroke
chosen
Pembroke is a small Canadian city in eastern Ontario known for its location along the Ottawa River and its role as a regional service and cultural center.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec72ea9348190817efcdaa973d7f7 |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb8bcc188190901e3f692fd8fbf9 |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.