Triple
T25489994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cochin royal family |
E638811
|
entity |
| Predicate | portCityOfRealm |
P158593
|
FINISHED |
| Object | Cochin (Kochi) |
—
|
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: Cochin (Kochi) | Statement: [Cochin royal family, portCityOfRealm, Cochin (Kochi)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portCityOfRealm Context triple: [Cochin royal family, portCityOfRealm, Cochin (Kochi)]
-
A.
capitalOfHisKingdom
Indicates that one entity serves as the capital city of the kingdom ruled or possessed by another entity.
-
B.
capitalCityBuildingOf
Indicates that a building is located in and associated with the capital city of a given political or administrative entity.
-
C.
cityOfFictionalLocation
Indicates that a fictional location is situated within or associated with a particular city.
-
D.
capitalCityLocatedOn
Indicates that a capital city is situated on or directly adjacent to a specific geographic feature, such as a river, coast, or lake.
-
E.
capitalLikeCity
Indicates that a capital city shares similar characteristics or status to a particular city.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7a4658081908758aa293923090d |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:34 p.m.