Triple
T17268382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Javanese inscriptions |
E419188
|
entity |
| Predicate | earliestExamplesDateFrom |
P64188
|
FINISHED |
| Object | 8th century CE |
—
|
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: 8th century CE | Statement: [Old Javanese inscriptions, earliestExamplesDateFrom, 8th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestExamplesDateFrom Context triple: [Old Javanese inscriptions, earliestExamplesDateFrom, 8th century CE]
-
A.
earliestWellKnownExample
Indicates that one entity is the earliest well-known example or instance of the other entity.
-
B.
earliestStructuresDateFrom
Indicates that the earliest known structures associated with an entity originate or were first constructed in a specified time period or date.
-
C.
earliestCarvingsDateFrom
Indicates the earliest known date from which the carvings are believed to originate.
-
D.
earliestStrataDate
Indicates the earliest known or recorded date associated with a particular geological or archaeological stratum.
-
E.
earliestDate
chosen
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
- 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.