Triple
T26811665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krishna Mandir |
E672012
|
entity |
| Predicate | hasArcadeOfColumns |
P18962
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Krishna Mandir, hasArcadeOfColumns, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArcadeOfColumns Context triple: [Krishna Mandir, hasArcadeOfColumns, yes]
-
A.
hasArcades
Indicates that one entity features or contains arcaded structures (a series of arches or covered passageways) associated with another entity.
-
B.
hasColonnade
chosen
Indicates that one entity features or is characterized by a colonnade in relation to another entity.
-
C.
arcadeStandard
Indicates that something conforms to, or is defined as, the standard or typical form used in arcade contexts (such as games, machines, or configurations).
-
D.
arcadeBoardRelation
Indicates a relationship between an arcade machine and the specific game board or hardware it uses or is associated with.
-
E.
numberOfColumnsInColonnade
Indicates the count of individual columns that make up a given colonnade.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 4:29 a.m.