Triple
T31409440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Âsım |
E801219
|
entity |
| Predicate | scriptCurrentlyPrintedIn |
P22941
|
FINISHED |
| Object | Latin Turkish alphabet |
—
|
NE NERFINISHED |
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: Latin Turkish alphabet | Statement: [Âsım, scriptCurrentlyPrintedIn, Latin Turkish alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptCurrentlyPrintedIn Context triple: [Âsım, scriptCurrentlyPrintedIn, Latin Turkish alphabet]
-
A.
scriptUsedCurrently
chosen
Indicates that a particular writing system or script is the one presently in use for a given language, text, or context.
-
B.
scriptName
Indicates the name or title of a script associated with an entity, typically identifying which script is used, referenced, or executed in a given context.
-
C.
scriptDeclared
Indicates that a script has been explicitly defined or specified for an entity or within a given context.
-
D.
scriptSource
Indicates that one entity is the origin or provider of the script used or referenced by another entity.
-
E.
scriptTarget
Indicates that one entity serves as the target or recipient of a script or scripted action initiated by another entity.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 30, 2026, 8:36 p.m.