Triple
T27416123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhirna zone |
E692898
|
entity |
| Predicate | entryFrom |
P12839
|
FINISHED |
| Object | Ramnagar |
—
|
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: Ramnagar | Statement: [Jhirna zone, entryFrom, Ramnagar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryFrom Context triple: [Jhirna zone, entryFrom, Ramnagar]
-
A.
entryFor
Indicates that one entity serves as the specific record, representation, or listing corresponding to another entity.
-
B.
entersFrom
chosen
Indicates that one entity moves into or arrives at a place, state, or context by coming from another specified source or location.
-
C.
enteredIntoBy
Indicates that an agreement, contract, or formal arrangement has been initiated or established by a particular party.
-
D.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
-
E.
enteredBy
Indicates that one entity has been input, recorded, or submitted into a system, record, or context by another entity.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d19c9d88190938cdcd21112fc69 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:34 p.m.