Triple
T6711487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigalari script |
E153152
|
entity |
| Predicate | hasScriptClass |
P28229
|
FINISHED |
| Object | Indic script |
—
|
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: Indic script | Statement: [Tigalari script, hasScriptClass, Indic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptClass Context triple: [Tigalari script, hasScriptClass, Indic script]
-
A.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
B.
hasScriptUsage
Indicates that one entity uses, employs, or is written in the script or writing system specified by another entity.
-
C.
hasScriptStatus
Indicates that an entity has a particular script-related state or condition, such as whether a script is present, active, or in a given status.
-
D.
hasScriptRegulator
Indicates that an entity has an associated mechanism or component that controls or governs its script or scripting behavior.
-
E.
hasCoreClass
chosen
Indicates that an entity is associated with, or belongs to, a primary or fundamental class within a classification system.
- 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_69c68808d8d8819087369015270788fe |
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:06 p.m.