Triple
T28103168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kthi |
E710288
|
entity |
| Predicate | scriptHistoricalUse |
P4037
|
FINISHED |
| Object | administrative documents |
—
|
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: administrative documents | Statement: [Kthi, scriptHistoricalUse, administrative documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptHistoricalUse Context triple: [Kthi, scriptHistoricalUse, administrative documents]
-
A.
historicalFunction
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
B.
estimatedHistory
Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
-
C.
historicalScript
chosen
Indicates that an entity is or was written in, or otherwise associated with, a particular historical writing system or script.
-
D.
towerUseHistorical
Indicates that a tower has been used for historical purposes or holds significance due to its historical use.
-
E.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 9:06 p.m.