Triple
T26335214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Curios |
E662500
|
entity |
| Predicate | hasAuthorialPeriod |
P90217
|
FINISHED |
| Object | Weimar Republic era |
—
|
NE NERFINISHED |
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: Weimar Republic era | Statement: [Chinese Curios, hasAuthorialPeriod, Weimar Republic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorialPeriod Context triple: [Chinese Curios, hasAuthorialPeriod, Weimar Republic era]
-
A.
hasAuthorAtTimeOfWriting
Indicates that a work is associated with a specific author as they were at the particular time the work was written.
-
B.
workPeriodOfAuthorDescribed
Indicates that the time period during which an author was active or produced work is being described.
-
C.
hasCreativePeriod
chosen
Indicates that an entity is associated with a specific span of time during which it produced or engaged in notable creative work.
-
D.
hasAuthorialBackground
Indicates that an entity has a creator or author with a specific background, context, or set of characteristics associated with them.
-
E.
hasAuthor
Indicates that an entity is written or created by a specific author.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 26, 2026, 10:36 p.m.