Triple
T8275574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mormon Row Historic District |
E193537
|
entity |
| Predicate | foundingCommunity |
P8500
|
FINISHED |
| Object | Mormon settlers |
—
|
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: Mormon settlers | Statement: [Mormon Row Historic District, foundingCommunity, Mormon settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingCommunity Context triple: [Mormon Row Historic District, foundingCommunity, Mormon settlers]
-
A.
foundedCommunity
chosen
Indicates that an entity established or created a community, organization, or group.
-
B.
originCommunity
Indicates the community, group, or locality from which an entity originally comes or is derived.
-
C.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
-
D.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
-
E.
isCommunityOf
Indicates that one entity functions as a community composed of, or defined by, the members or elements represented by the other entity.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb798d69508190b581ad8a38730175 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:51 p.m.