Triple
T17100664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panjalu |
E414970
|
entity |
| Predicate | knownAsMajorPowerIn |
P404
|
FINISHED |
| Object | eastern Java |
—
|
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: eastern Java | Statement: [Panjalu, knownAsMajorPowerIn, eastern Java]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownAsMajorPowerIn Context triple: [Panjalu, knownAsMajorPowerIn, eastern Java]
-
A.
majorPowerIn
chosen
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
-
B.
countryOfNotableSuccess
Indicates the country in which an entity achieved notable success or recognition.
-
C.
wasRegionalPower
Indicates that an entity held significant political, military, or economic influence within a specific geographic region during a particular historical period.
-
D.
countryKnownFor
Indicates that a country is widely recognized or notable for a particular characteristic, product, activity, or feature.
-
E.
geopoliticalRole
Indicates the specific political or strategic function, status, or position an entity holds within or among geopolitical units such as states, regions, or international organizations.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc0182cc8190b8aa9c980f11ba57 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.