Triple
T33259012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daylesford with Adlestrop |
E851456
|
entity |
| Predicate | unitesCommunityOf |
P35250
|
FINISHED |
| Object | Daylesford |
—
|
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: Daylesford | Statement: [Daylesford with Adlestrop, unitesCommunityOf, Daylesford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitesCommunityOf Context triple: [Daylesford with Adlestrop, unitesCommunityOf, Daylesford]
-
A.
unites
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
-
B.
isCommunityOf
Indicates that one entity functions as a community composed of, or defined by, the members or elements represented by the other entity.
-
C.
connectsCommunities
chosen
Indicates a relationship in which something links or brings together separate communities, enabling interaction, communication, or shared activity between them.
-
D.
oftenUnitedWith
Indicates that two entities are frequently joined, combined, or associated together as a common or recurring unit.
-
E.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:31 a.m.