Triple
T25422012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saka era |
E637008
|
entity |
| Predicate | scriptOfTraditionalNotation |
P4882
|
FINISHED |
| Object | Devanagari |
—
|
NE NERFINISHED |
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: Devanagari | Statement: [Saka era, scriptOfTraditionalNotation, Devanagari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptOfTraditionalNotation Context triple: [Saka era, scriptOfTraditionalNotation, Devanagari]
-
A.
scriptOfNotes
Indicates that one entity is the written or notated script (e.g., musical, theatrical, or instructional notes) that documents, guides, or underlies another entity.
-
B.
typicalNotation
chosen
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
C.
sequenceNotation
Indicates that one entity specifies the ordered symbolic representation (notation) used to express a sequence associated with another entity.
-
D.
appearsInNotation
Indicates that one entity is represented, referenced, or depicted within the formal notation or symbolic system associated with another entity.
-
E.
musicScoreBy
Indicates that a musical score was created or composed by a particular agent or entity.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bd517c819086c0e8e9c2dce972 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:56 p.m.