Triple
T5554104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takri script |
E145594
|
entity |
| Predicate | usedForAdministrativePurposes |
P64442
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Takri script, usedForAdministrativePurposes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForAdministrativePurposes Context triple: [Takri script, usedForAdministrativePurposes, yes]
-
A.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
C.
administrativelyIn
Indicates that one entity is located within or belongs to the jurisdiction or governance area of another entity for administrative purposes.
-
D.
administeredFor
Indicates that something (typically a treatment, medication, or intervention) is given or applied to an entity for a specific purpose, condition, or intended effect.
-
E.
usedForService
Indicates that one entity is employed, utilized, or designated to perform, support, or provide a particular service for another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:36 p.m.