Triple
T34524039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flora Fountain |
E886352
|
entity |
| Predicate | squareRenamedAs |
P137525
|
FINISHED |
| Object | Hutatma Chowk |
—
|
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: Hutatma Chowk | Statement: [Flora Fountain, squareRenamedAs, Hutatma Chowk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: squareRenamedAs Context triple: [Flora Fountain, squareRenamedAs, Hutatma Chowk]
-
A.
squareOriginalName
Indicates that the entity’s name is the original, canonical name of a square (e.g., a public square or plaza), as opposed to an alternate or derived name.
-
B.
squareUse
Indicates that one entity uses or occupies another entity in a square or rectangular configuration, typically implying a grid-like or evenly spaced arrangement.
-
C.
squareNamedAfter
chosen
Indicates that a public square is named in honor of, or derived its name from, a particular person, place, event, or entity.
-
D.
squareType
Indicates that one entity is classified as a specific type or category of square in relation to another entity.
-
E.
squareGivenBy
Indicates that one entity is a square (or square-shaped region) that has been specified, defined, or provided 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb5aa008190a40453a4139851b3 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.