Triple
T30572543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kül Tigin |
E778155
|
entity |
| Predicate | scriptUsedInMonument |
P159127
|
FINISHED |
| Object | Old Turkic script |
—
|
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: Old Turkic script | Statement: [Kül Tigin, scriptUsedInMonument, Old Turkic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptUsedInMonument Context triple: [Kül Tigin, scriptUsedInMonument, Old Turkic script]
-
A.
scriptUsedInMonuments
chosen
Indicates that a particular writing system or script is employed in the inscriptions or textual elements found on specific monuments.
-
B.
usedInMonument
Indicates that something serves as a material, component, or element incorporated into the construction or design of a monument.
-
C.
appliesToMonument
Indicates that something (such as a rule, status, or attribute) is relevant or applicable specifically to a monument.
-
D.
hasMonumentFunction
Indicates that something serves the role or purpose of a monument, such as commemorating, honoring, or symbolizing a person, event, or idea.
-
E.
hasScheduledMonument
Indicates that an entity is associated with, or contains, a site or structure officially designated as a scheduled monument.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 29, 2026, 8:22 p.m.