Triple
T36248732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YWB |
E891735
|
entity |
| Predicate | associatedCommunityType |
P3292
|
FINISHED |
| Object | Inuit 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: Inuit community | Statement: [YWB, associatedCommunityType, Inuit community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCommunityType Context triple: [YWB, associatedCommunityType, Inuit community]
-
A.
associatedCommunity
Indicates a relationship where an entity is linked or connected to a particular community with which it is involved or identified.
-
B.
relationshipWithCommunity
Indicates a connection or association that an entity has with a particular community, such as involvement, affiliation, or engagement.
-
C.
hasCommunityType
chosen
Indicates that an entity is associated with or classified under a particular type or category of community.
-
D.
formedCommunityWith
Indicates that two or more entities came together to establish or join the same community or collective group.
-
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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.