Triple
T2130743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaker Village of Pleasant Hill |
E46532
|
entity |
| Predicate | foundedAsCommunity |
P364
|
FINISHED |
| Object | 1805 |
—
|
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: 1805 | Statement: [Shaker Village of Pleasant Hill, foundedAsCommunity, 1805]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCommunity Context triple: [Shaker Village of Pleasant Hill, foundedAsCommunity, 1805]
-
A.
foundedCommunity
Indicates that an entity established or created a community, organization, or group.
-
B.
foundedAs
chosen
Indicates the original name or form under which an organization, institution, or entity was first established.
-
C.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
D.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
-
E.
foundedAsResultOf
Indicates that one entity was established or created as a direct consequence or outcome of another event, action, or circumstance.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb79f21881909ad8d1a09c1f29fd |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.