Triple
T18096887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerusalem in Miniature |
E433111
|
entity |
| Predicate | hasCreatorBirthplace |
P90944
|
FINISHED |
| Object | Germany (for Brother Joseph Zoettl) |
—
|
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: Germany (for Brother Joseph Zoettl) | Statement: [Jerusalem in Miniature, hasCreatorBirthplace, Germany (for Brother Joseph Zoettl)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreatorBirthplace Context triple: [Jerusalem in Miniature, hasCreatorBirthplace, Germany (for Brother Joseph Zoettl)]
-
A.
creatorPlaceOfBirth
chosen
Indicates that the place specified is the location where the creator of an entity was born.
-
B.
creatorLivedIn
Indicates that the person who created a work resided in a particular place for some period of time.
-
C.
isBirthplaceRelatedTo
Indicates that there is a relationship between an entity and a birthplace, such as being born there or otherwise closely associated with that place of birth.
-
D.
containsBirthplaceTown
Indicates that one entity includes or specifies the town where another entity was born.
-
E.
nearBirthplaceOf
Indicates that one entity is located close to the place where another entity was born.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd1de6f48190a3fefd02a4b2ab58 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.