Triple
T36962177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreisau Circle |
E914333
|
entity |
| Predicate | formedInYearApprox |
P13193
|
FINISHED |
| Object | 1940 |
—
|
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: 1940 | Statement: [Kreisau Circle, formedInYearApprox, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedInYearApprox Context triple: [Kreisau Circle, formedInYearApprox, 1940]
-
A.
formedInYear
Indicates the year in which an entity was originally established, created, or came into existence.
-
B.
formedBeforeYear
Indicates that an entity was formed or came into existence earlier than a specified calendar year.
-
C.
approximateBirthYear
Indicates that the associated year is an estimated or inferred value for when an entity was born, rather than an exact known birth year.
-
D.
approximateStartYear
chosen
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
E.
endYearApprox
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00b7fb90f881908f73edf2be8cc3a5 |
completed | May 10, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_6a00b75593d08190b3e76191cd79cdec |
completed | May 10, 2026, 4:50 p.m. |
Created at: May 3, 2026, 4:14 p.m.