Triple
T19240843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalkin |
E481126
|
entity |
| Predicate | traditionalBirthplaceType |
P135317
|
FINISHED |
| Object | mythical city |
—
|
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: mythical city | Statement: [Kalkin, traditionalBirthplaceType, mythical city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalBirthplaceType Context triple: [Kalkin, traditionalBirthplaceType, mythical city]
-
A.
placeOfBirth
Indicates the location where a person or other entity was born.
-
B.
containsBirthplaceTown
Indicates that one entity includes or specifies the town where another entity was born.
-
C.
houseByBirth
Indicates that an entity belongs to or is associated with a particular house or lineage by virtue of birth.
-
D.
namedAfterBirthPlace
Indicates that an entity is given a name derived from or based on the place where it was born.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faf14564819085009adf822804ab |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4debc39ac81908b7c5ef797046360 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:26 p.m.