Triple
T26807716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millbrook |
E671886
|
entity |
| Predicate | sharesRegionalCommunityTiesWith |
P117178
|
FINISHED |
| Object | Somerton |
—
|
NE NERFINISHED |
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: Somerton | Statement: [Millbrook, sharesRegionalCommunityTiesWith, Somerton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesRegionalCommunityTiesWith Context triple: [Millbrook, sharesRegionalCommunityTiesWith, Somerton]
-
A.
associatedCommunity
Indicates a relationship where an entity is linked or connected to a particular community with which it is involved or identified.
-
B.
sharesCommunityWith
Indicates that two entities belong to or participate in the same community or communal group.
-
C.
isCommunityOf
Indicates that one entity functions as a community composed of, or defined by, the members or elements represented by the other entity.
-
D.
shareRegionalIdentityWith
chosen
Indicates that two entities are perceived to belong to or identify with the same geographic, cultural, or regional community.
-
E.
connectsCommunities
Indicates a relationship in which something links or brings together separate communities, enabling interaction, communication, or shared activity between them.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 27, 2026, 4:27 a.m.