Triple
T5554091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takri script |
E145594
|
entity |
| Predicate | currentUsageStatus |
P50271
|
FINISHED |
| Object | limited contemporary use |
—
|
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: limited contemporary use | Statement: [Takri script, currentUsageStatus, limited contemporary use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentUsageStatus Context triple: [Takri script, currentUsageStatus, limited contemporary use]
-
A.
administrativeStatusCurrent
Indicates the current administrative status or condition of an entity within a governing or managing system.
-
B.
currentStatusSince
Indicates the point in time since which an entity has held its current status or state.
-
C.
availabilityStatus
chosen
Indicates the current state of whether something is obtainable, usable, or accessible at a given time.
-
D.
isFreeToUse
Indicates that something can be used without cost, restriction, or required permission.
-
E.
isInUse
Indicates that an entity is currently being utilized or actively engaged in its intended function or operation.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ff9c9c48190b5e587d58c6515d8 |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.