Triple
T6712694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gupta script |
E153184
|
entity |
| Predicate | scriptCharacteristics |
P56672
|
FINISHED |
| Object | consonant-based with inherent vowel |
—
|
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: consonant-based with inherent vowel | Statement: [Gupta script, scriptCharacteristics, consonant-based with inherent vowel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptCharacteristics Context triple: [Gupta script, scriptCharacteristics, consonant-based with inherent vowel]
-
A.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
-
B.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
C.
scopeCharacterization
Indicates how the extent, boundaries, or coverage of something is defined, described, or qualified in relation to another entity or context.
-
D.
describesCharacteristicOf
chosen
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
-
E.
campaignCharacteristics
Indicates the defining features, attributes, or qualities that characterize a particular campaign.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d121a92c8190a03f384a8aba84da |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.