Triple
T19406626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kushika dynasty |
E485478
|
entity |
| Predicate | statusInTexts |
P134245
|
FINISHED |
| Object | semi-legendary |
—
|
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: semi-legendary | Statement: [Kushika dynasty, statusInTexts, semi-legendary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInTexts Context triple: [Kushika dynasty, statusInTexts, semi-legendary]
-
A.
statusInText
chosen
Indicates that the text explicitly states or conveys the status or condition of an entity.
-
B.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
C.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
D.
textStatus
Indicates the current state or condition of a piece of text, such as its progress, validity, or processing outcome.
-
E.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6257bad0c819088dd7729b6a36a94 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.