Triple
T22050235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangut Components |
E544862
|
entity |
| Predicate | timeOfHistoricalUse |
P3656
|
FINISHED |
| Object | 11th–13th centuries |
—
|
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: 11th–13th centuries | Statement: [Tangut Components, timeOfHistoricalUse, 11th–13th centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfHistoricalUse Context triple: [Tangut Components, timeOfHistoricalUse, 11th–13th centuries]
-
A.
historicalPeriodOfUse
chosen
Indicates the time period during which something was in active use or commonly utilized.
-
B.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
-
C.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
periodOfMajorUse
Indicates the time span during which something was primarily or most intensively used.
-
E.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128323fb08190b9592fd08a96cba0 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.