Triple
T14231685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumpah Palapa |
E352765
|
entity |
| Predicate | mentionedPlaces |
P10233
|
FINISHED |
| Object | Gurun |
—
|
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: Gurun | Statement: [Sumpah Palapa, mentionedPlaces, Gurun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedPlaces Context triple: [Sumpah Palapa, mentionedPlaces, Gurun]
-
A.
places
Indicates that one entity assigns, positions, or puts another entity into a specific location, role, or context.
-
B.
placesInQuestion
Indicates that an entity is located within, or occurs in, the spatial or contextual scope defined by a given question.
-
C.
promotionPlaces
Indicates that one entity designates or assigns another entity to a higher position, rank, or status within some organizational or hierarchical structure.
-
D.
relatedPlace
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
-
E.
notablePlace
chosen
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622cdd6481908befa179a9675bb5 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.