Triple
T19570379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Burrows |
E489693
|
entity |
| Predicate | isInCommunity |
P129321
|
FINISHED |
| Object | Cimla community |
—
|
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: Cimla community | Statement: [The Burrows, isInCommunity, Cimla community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCommunity Context triple: [The Burrows, isInCommunity, Cimla community]
-
A.
isCommunityBy
Indicates that something functions as or is recognized as a community defined or established by a particular agent or source.
-
B.
isCommunity
chosen
Indicates that an entity functions as or is classified as a community, typically representing a group of individuals connected by shared location, interests, or characteristics.
-
C.
hasRoleInCommunity
Indicates that an entity holds or performs a specific role, function, or position within a particular community.
-
D.
isPartOfCommunityIdentity
Indicates that something contributes to, represents, or is recognized as a defining element of a community’s shared identity.
-
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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402043588190a99f5a55c5dcd8a6 |
completed | April 20, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.