Triple
T33236218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maithil community |
E850835
|
entity |
| Predicate | traditionalRegionCity |
P174333
|
FINISHED |
| Object | Darbhanga |
—
|
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: Darbhanga | Statement: [Maithil community, traditionalRegionCity, Darbhanga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRegionCity Context triple: [Maithil community, traditionalRegionCity, Darbhanga]
-
A.
terminalCityRegion
Indicates that a city serves as the terminal (end-point) location within a specified region for a route, line, or connection.
-
B.
capitalCityOfRegion
Indicates that a city serves as the official capital of a specified region, functioning as its primary administrative or governmental center.
-
C.
linkedCityRegion
chosen
Indicates that a city is associated with, belongs to, or is administratively connected to a specific region.
-
D.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
E.
cityServedRegion
Indicates that a city provides services to, or functions as an administrative or economic center for, a specified region.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 1:31 a.m.