Triple
T26235061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacKillop |
E656141
|
entity |
| Predicate | includesCommunitiesType |
P8617
|
FINISHED |
| Object | rural towns |
—
|
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: rural towns | Statement: [MacKillop, includesCommunitiesType, rural towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCommunitiesType Context triple: [MacKillop, includesCommunitiesType, rural towns]
-
A.
includesCommunitiesFrom
Indicates that one entity encompasses or contains communities that originate from or belong to another entity.
-
B.
includesInSomeCommunities
Indicates that an entity is considered a member or part of certain, but not necessarily all, communities.
-
C.
includesCommunity
chosen
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
-
D.
hasCommunityType
Indicates that an entity is associated with or classified under a particular type or category of community.
-
E.
appliesToCommunity
Indicates that something (such as a rule, policy, feature, or condition) is relevant or applicable to a particular community as a whole.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 26, 2026, 9:01 p.m.