Triple
T26280232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutadgu Bilig |
E660681
|
entity |
| Predicate | notableManuscriptLocation |
P99143
|
FINISHED |
| Object | Vienna |
—
|
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: Vienna | Statement: [Kutadgu Bilig, notableManuscriptLocation, Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableManuscriptLocation Context triple: [Kutadgu Bilig, notableManuscriptLocation, Vienna]
-
A.
notableManuscriptSource
Indicates that one entity serves as a significant or historically important manuscript source for another entity.
-
B.
manuscriptFoundIn
chosen
Indicates that a manuscript is discovered or located within a particular place, collection, or context.
-
C.
originalManuscriptLocation
Indicates the place where the original version of a manuscript is physically kept or stored.
-
D.
notableManuscriptFeature
Indicates that a manuscript possesses a specific distinguishing characteristic, attribute, or element that is considered noteworthy or significant.
-
E.
manuscriptDiscoveredBy
Indicates that a manuscript was found or brought to light through the efforts or actions of a particular agent or 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 26, 2026, 9:59 p.m.