Triple
T15470247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sasti |
E372139
|
entity |
| Predicate | hasStatusInCommunity |
P38813
|
FINISHED |
| Object | heritage language |
—
|
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: heritage language | Statement: [Sasti, hasStatusInCommunity, heritage language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusInCommunity Context triple: [Sasti, hasStatusInCommunity, heritage language]
-
A.
statusInCommunity
chosen
Indicates the social standing, role, or level of acceptance an entity holds within a particular community.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasRoleInCommunity
Indicates that an entity holds or performs a specific role, function, or position within a particular community.
-
D.
statusOfCommunity
Indicates the current condition, state, or standing of a community at a given point in time.
-
E.
hasTargetCommunity
Indicates that something is specifically intended for, directed toward, or designed to serve a particular community or group.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6b49788190b270fdfe92646842 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.