Triple
T33431951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarati |
E856152
|
entity |
| Predicate | hasNotationFor |
P95660
|
FINISHED |
| Object | consonants |
—
|
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: consonants | Statement: [Sarati, hasNotationFor, consonants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotationFor Context triple: [Sarati, hasNotationFor, consonants]
-
A.
usesNotationFor
chosen
Indicates that one entity employs or adopts a particular notation system or symbolic representation for another entity.
-
B.
hasNameInNotation
Indicates that an entity is referred to by a specific name or label within a particular notation or symbolic system.
-
C.
hasObjectNotation
Indicates that an entity is represented or expressed using a specific object-based notation or symbolic format.
-
D.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
E.
languageOfNotation
Indicates the language in which a given notation, script, or symbolic system is expressed or encoded.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01bcd39760819081807a02eb1939d1 |
completed | May 11, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_6a01bc3f1c74819087580e3134affc60 |
completed | May 11, 2026, 11:23 a.m. |
Created at: May 1, 2026, 1:36 a.m.