Triple
T26994987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rawla Mandi |
E679957
|
entity |
| Predicate | hasLocalNameElement |
P150492
|
FINISHED |
| Object | Mandi indicates market town |
—
|
LITERAL 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: Mandi indicates market town | Statement: [Rawla Mandi, hasLocalNameElement, Mandi indicates market town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalNameElement Context triple: [Rawla Mandi, hasLocalNameElement, Mandi indicates market town]
-
A.
hasLocalName
Indicates that an entity is known by a specific name or designation within a particular local language, script, or regional context.
-
B.
hasLocalNameFor
Indicates that one entity serves as the local or context-specific name or label used to refer to another entity.
-
C.
hasProperNameElement
chosen
Indicates that an entity’s proper name includes a specific component (such as a word, phrase, or segment) as one of its constituent elements.
-
D.
mayHaveLocalName
Indicates that an entity can optionally be associated with a locally used or context-specific name.
-
E.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 6:54 a.m.