Triple
T36824214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghodageri |
E909965
|
entity |
| Predicate | knownAsBirthplaceOf |
P1
|
FINISHED |
| Object | Chandrashekhara Kambara |
—
|
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: Chandrashekhara Kambara | Statement: [Ghodageri, knownAsBirthplaceOf, Chandrashekhara Kambara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownAsBirthplaceOf Context triple: [Ghodageri, knownAsBirthplaceOf, Chandrashekhara Kambara]
-
A.
placeOfBirth
chosen
Indicates the location where a person or other entity was born.
-
B.
nearBirthplaceOf
Indicates that one entity is located close to the place where another entity was born.
-
C.
cityOfBirthOfNamesake
Indicates that one entity is the city where the namesake (the person or entity after whom something is named) of another entity was born.
-
D.
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.
-
E.
capitalCityOfOriginCountry
Indicates that a city is the capital of the country from which an entity (such as a person, organization, or product) originates.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca9a6b2c8190a27a5c3f91a74d03 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.