Triple
T10615552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakrapani Temple |
E276108
|
entity |
| Predicate | hasPrakara |
P72825
|
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: [Chakrapani Temple, hasPrakara, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrakara Context triple: [Chakrapani Temple, hasPrakara, yes]
-
A.
hasMarae
Indicates a relationship where an entity possesses, contains, or is associated with a marae (a Māori meeting place or communal space).
-
B.
hasParapet
Indicates that an object, structure, or area is equipped with or bounded by a parapet (a low protective wall or barrier along an edge).
-
C.
hasMoat
Indicates that one entity is surrounded or protected by a moat associated with another entity.
-
D.
hasTamga
Indicates that an entity bears or is marked with a specific tamga (a distinctive emblem, brand, or clan/ownership mark).
-
E.
hasMandapa
chosen
Indicates that a structure (typically a temple) includes or is associated with a mandapa, an attached or nearby pillared hall or pavilion used for rituals or gatherings.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df6d76dc8190bd8d481fed3225d9 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:33 p.m.