Triple
T26642449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prakasam district |
E668816
|
entity |
| Predicate | hasMajorPortTown |
P100369
|
FINISHED |
| Object | Chirala |
—
|
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: Chirala | Statement: [Prakasam district, hasMajorPortTown, Chirala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorPortTown Context triple: [Prakasam district, hasMajorPortTown, Chirala]
-
A.
hasMajorSeaPort
Indicates that a place possesses at least one significant seaport used for major maritime transport, trade, or shipping activities.
-
B.
isPortTown
chosen
Indicates that a town is located on or near a navigable body of water and functions as a port for maritime or river transport and trade.
-
C.
isMajorSeaport
Indicates that a location functions as a primary maritime port handling significant volumes of sea-based trade, transport, or shipping activity.
-
D.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
-
E.
majorPortCity
Indicates that a city functions as a primary maritime port, serving as a major hub for sea transport, trade, or shipping activities.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 27, 2026, 2:29 a.m.