Triple
T2314879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taliq script |
E51039
|
entity |
| Predicate | scriptCodeStatus |
P9329
|
FINISHED |
| Object | not separately encoded in Unicode |
—
|
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: not separately encoded in Unicode | Statement: [Taliq script, scriptCodeStatus, not separately encoded in Unicode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptCodeStatus Context triple: [Taliq script, scriptCodeStatus, not separately encoded in Unicode]
-
A.
scriptCode
chosen
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
B.
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.
-
C.
programStatus
Indicates the current state or condition of a program within its lifecycle (e.g., planned, active, paused, completed, or terminated).
-
D.
compilationStatus
Indicates the current state or outcome of a compilation process for a given entity (e.g., whether it is pending, in progress, successful, or failed).
-
E.
scriptCodeRole
Indicates the role or function that a particular script code plays within a given context or 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.