Triple
T17268360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Javanese inscriptions |
E419188
|
entity |
| Predicate | oftenRecord |
P31723
|
FINISHED |
| Object | royal charters |
—
|
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: royal charters | Statement: [Old Javanese inscriptions, oftenRecord, royal charters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenRecord Context triple: [Old Javanese inscriptions, oftenRecord, royal charters]
-
A.
oftenSays
Indicates that one entity frequently makes a particular statement or remark, or regularly expresses a certain idea or phrase.
-
B.
isOftenRecordedWith
chosen
Indicates that one entity is frequently documented, captured, or logged at the same time as another entity.
-
C.
oftenHave
Indicates that one entity frequently possesses, experiences, or is associated with another entity.
-
D.
frequentlyRecordedBy
Indicates that an entity is often documented, captured, or logged by a particular agent, system, or recording process.
-
E.
isFrequentlyRecorded
Indicates that an entity is captured or documented many times within a given dataset, medium, or context.
- 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.