Triple
T6565218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumi script |
E153885
|
entity |
| Predicate | primaryScriptFor |
P55012
|
FINISHED |
| Object | modern Malay |
—
|
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: modern Malay | Statement: [Rumi script, primaryScriptFor, modern Malay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryScriptFor Context triple: [Rumi script, primaryScriptFor, modern Malay]
-
A.
primaryScript
Indicates the writing system or script that is chiefly used to represent the language or content of an entity.
-
B.
primaryFor
chosen
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
C.
primaryFile
Indicates that one file in a set is designated as the main or most important file associated with a given entity or context.
-
D.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
E.
previousPrimaryScriptingLanguage
Indicates that an entity was formerly the main or primary scripting language used by another entity before being replaced or superseded.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:52 p.m.