Triple
T569249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kawi script |
E13623
|
entity |
| Predicate | usedForManuscripts |
P98
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kawi script, usedForManuscripts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForManuscripts Context triple: [Kawi script, usedForManuscripts, true]
-
A.
scholarlyUse
Indicates that something is used for academic, educational, or research-related purposes.
-
B.
usedDocument
Indicates that one entity has employed, referenced, or otherwise made use of a particular document in performing an action or fulfilling a purpose.
-
C.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
usedResearchFrom
Indicates that one entity based its work, findings, or outputs on research conducted or provided by another entity.
-
E.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b0406d481908af5fc7bc67103fb |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c2caac819086ab316fa49d324c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.