Triple
T31131170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 12.0 |
E793510
|
entity |
| Predicate | includesHistoricScript |
P4037
|
FINISHED |
| Object | Nandinagari |
—
|
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: Nandinagari | Statement: [Unicode 12.0, includesHistoricScript, Nandinagari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesHistoricScript Context triple: [Unicode 12.0, includesHistoricScript, Nandinagari]
-
A.
includesHistoricResource
Indicates that one entity contains, encompasses, or otherwise has within its scope a historic resource.
-
B.
includesHistoricSee
Indicates that something contains or encompasses a historically significant site, feature, or point of interest.
-
C.
historicalScript
chosen
Indicates that an entity is or was written in, or otherwise associated with, a particular historical writing system or script.
-
D.
includeHistoricalSee
Indicates that a relationship or reference should also encompass or display historically related "see also" connections or pointers.
-
E.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00c3362dcc819096e49b882709fddd |
completed | May 10, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_6a00c2e5cdd88190a5f2d0f6a843cd56 |
completed | May 10, 2026, 5:39 p.m. |
Created at: April 29, 2026, 9:05 p.m.