Triple
T26227437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mughalsarai district |
E655932
|
entity |
| Predicate | hasProposedNameOrigin |
P3325
|
FINISHED |
| Object | Mughalsarai town |
—
|
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: Mughalsarai town | Statement: [Mughalsarai district, hasProposedNameOrigin, Mughalsarai town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProposedNameOrigin Context triple: [Mughalsarai district, hasProposedNameOrigin, Mughalsarai town]
-
A.
hasProposedOrigins
Indicates that there are suggested or hypothesized sources, beginnings, or origins for something, typically based on theory or evidence rather than certainty.
-
B.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
-
C.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
-
D.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
E.
hasProposedMethod
Indicates that an entity has put forward or suggested a specific method as a solution, approach, or procedure in a given context.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 26, 2026, 8:58 p.m.