Triple
T17268352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Javanese inscriptions |
E419188
|
entity |
| Predicate | mainlyFoundIn |
P9687
|
FINISHED |
| Object | 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: Java | Statement: [Old Javanese inscriptions, mainlyFoundIn, Java]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainlyFoundIn Context triple: [Old Javanese inscriptions, mainlyFoundIn, Java]
-
A.
commonlyFoundOn
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
B.
traditionallyFoundIn
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
-
C.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
D.
discoveredInCountry
Indicates that something was discovered within the geographical boundaries or jurisdiction of a specified country.
-
E.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4683c4819083a210255662136c |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.