Triple
T26222672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jatiluhur |
E655804
|
entity |
| Predicate | hasFunctionForRegion |
P146793
|
FINISHED |
| Object | supports regional electricity supply |
—
|
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: supports regional electricity supply | Statement: [Jatiluhur, hasFunctionForRegion, supports regional electricity supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionForRegion Context triple: [Jatiluhur, hasFunctionForRegion, supports regional electricity supply]
-
A.
hasRegionFunction
Indicates that a region is associated with a particular function, role, or operational purpose.
-
B.
hasFunctionAtSite
chosen
Indicates that an entity performs or exhibits a specific function at a particular site or location.
-
C.
hasFunctionInPresent
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
-
D.
hasFunctionInContext
Indicates that an entity serves a particular role or performs a specific function within a given context or situation.
-
E.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d5127d48190b28c89797f2852f2 |
completed | May 2, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:56 p.m.