Triple
T5640271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shashmaqam |
E124247
|
entity |
| Predicate | wasCodifiedDuring |
P1127
|
FINISHED |
| Object | Soviet period |
—
|
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: Soviet period | Statement: [Shashmaqam, wasCodifiedDuring, Soviet period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCodifiedDuring Context triple: [Shashmaqam, wasCodifiedDuring, Soviet period]
-
A.
timeOfCodification
Indicates the specific point in time at which something (such as a rule, law, or concept) was formally codified or recorded.
-
B.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
C.
yearOfPromulgation
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
D.
enactedDuring
chosen
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
-
E.
legislatedOn
Indicates that a legislative body has formally considered, debated, or enacted laws or regulations concerning a particular subject 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022850bf08190953cd5394f821801 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.