Triple
T9147001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbo-Croatian |
E219480
|
entity |
| Predicate | standardizationBeganIn |
P33818
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Serbo-Croatian, standardizationBeganIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizationBeganIn Context triple: [Serbo-Croatian, standardizationBeganIn, 19th century]
-
A.
wasGraduallyStandardizedIn
Indicates that something became standardized or uniform within a particular context through a gradual, step-by-step process over time.
-
B.
timePeriodOfStandardization
Indicates the time span during which a particular standard was formally established or in effect.
-
C.
standardizedSince
chosen
Indicates that something has been formally standardized starting from a specific point in time.
-
D.
laterStandardization
Indicates that one entity becomes standardized or formally established at a later time than another entity.
-
E.
firstStandardized
Indicates that an entity is the earliest or primary instance to which a standard or uniform specification has been first applied among comparable entities.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca918a3c881909c34a6a682eb2625 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.