Triple
T23975178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B0K |
E604344
|
entity |
| Predicate | encompassesCommunity |
P8617
|
FINISHED |
| Object | Wallace, Nova Scotia |
—
|
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: Wallace, Nova Scotia | Statement: [B0K, encompassesCommunity, Wallace, Nova Scotia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encompassesCommunity Context triple: [B0K, encompassesCommunity, Wallace, Nova Scotia]
-
A.
includesCommunity
chosen
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
-
B.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
C.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
-
D.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
E.
includesCommunitiesFrom
Indicates that one entity encompasses or contains communities that originate from or belong to another 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2ba11708190b8587bd006249ff5 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:26 p.m.