Triple
T4230096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javanese script |
E94557
|
entity |
| Predicate | hasStandardOrdering |
P19744
|
FINISHED |
| Object | hanacaraka sequence |
—
|
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: hanacaraka sequence | Statement: [Javanese script, hasStandardOrdering, hanacaraka sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardOrdering Context triple: [Javanese script, hasStandardOrdering, hanacaraka sequence]
-
A.
hasColumnOrder
Indicates that one column in a sequence is positioned before or after another column, specifying their relative ordering.
-
B.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
C.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
D.
hasTextOrder
chosen
Indicates that there is a specified sequence or ordering of text elements relative to one another.
-
E.
hasSort
Indicates that one entity is associated with, or classified by, a particular sort, type, or category.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e61ccc081909b880baf1d6a0f24 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.