Triple
T20668629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rikkokushi |
E507958
|
entity |
| Predicate | timeSpanOfCompilation |
P98850
|
FINISHED |
| Object | early 8th century to late 9th 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: early 8th century to late 9th century | Statement: [Rikkokushi, timeSpanOfCompilation, early 8th century to late 9th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanOfCompilation Context triple: [Rikkokushi, timeSpanOfCompilation, early 8th century to late 9th century]
-
A.
timeOfCompilationContext
Indicates the specific time or temporal context in which a compilation process or compilation-related event occurs.
-
B.
compilationSpeed
Indicates how quickly a program or source code is processed and transformed into executable form by a compiler.
-
C.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
D.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
E.
eraOfCompilation
chosen
Indicates the historical time period during which something (such as a text, dataset, or work) was compiled or put together.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c60a2481908ae3764bc12454e0 |
completed | April 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.