Triple
T23149920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamba ware |
E578294
|
entity |
| Predicate | productionStartCentury |
P15335
|
FINISHED |
| Object | 12th 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: 12th century | Statement: [Tamba ware, productionStartCentury, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionStartCentury Context triple: [Tamba ware, productionStartCentury, 12th century]
-
A.
emergedByCentury
Indicates that something came into existence, became prominent, or first appeared during a specified century.
-
B.
originalCentury
chosen
Indicates the century in which something was originally created, produced, or came into existence.
-
C.
developedSinceCentury
Indicates that something began to be developed or came into existence starting from a specified century onward.
-
D.
constructionCentury
Indicates the century during which something was constructed or built.
-
E.
introducedInCentury
Indicates the century during which something (such as an idea, technology, practice, or entity) was first introduced or came into use.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ed0b76c8190ac61b949d88e9970 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.