Triple
T34847839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poker Flat |
E1004518
|
entity |
| Predicate | hasSocialType |
P11720
|
FINISHED |
| Object | frontier 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: frontier community | Statement: [Poker Flat, hasSocialType, frontier community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialType Context triple: [Poker Flat, hasSocialType, frontier community]
-
A.
hasSocialService
Indicates that an entity provides, offers, or is associated with a social service to another entity or community.
-
B.
hasSocialIdentity
chosen
Indicates that an entity possesses or is associated with a particular social identity, such as a role, group membership, or socially recognized status.
-
C.
socialType
Indicates the category or nature of a social relationship or interaction that exists between entities.
-
D.
hasSocialMessage
Indicates that something conveys, promotes, or is associated with a broader social, ethical, or political message.
-
E.
hasSocialEngagement
Indicates that an entity participates in or maintains some form of social interaction, activity, or relationship with others.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4 p.m.