Triple
T32134715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maithil |
E820738
|
entity |
| Predicate | associatedWithLegendaryCity |
P25162
|
FINISHED |
| Object | Janakpur (Janakpurdham) |
E254454
|
NE 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: Janakpur (Janakpurdham) | Statement: [Maithil, associatedWithLegendaryCity, Janakpur (Janakpurdham)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLegendaryCity Context triple: [Maithil, associatedWithLegendaryCity, Janakpur (Janakpurdham)]
-
A.
associatedWithCityHistory
Indicates a relationship where something is connected or relevant to the historical events, development, or heritage of a particular city.
-
B.
hasNearbyAncientCity
Indicates that one entity is located close to another entity that is classified as an ancient city.
-
C.
relatesToAncientCity
Indicates a relationship or connection between an entity and an ancient city, such as origin, location, influence, or relevance.
-
D.
associatedWithCityFoundedBy
Indicates a relationship where an entity is linked to the city that was founded by a specified person or group.
-
E.
hasAssociatedCity
chosen
Indicates that one entity is linked or related to a specific city, typically as its location, base, or primary area of association.
- F. None of above.
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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0bc81bf88190b3c96e748c85ffcb |
completed | June 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:30 a.m.