Triple
T12863515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Lady of the Immaculate Conception Church, Panaji |
E307655
|
entity |
| Predicate | hasStatuary |
P1646
|
FINISHED |
| Object | statue of the Virgin Mary |
—
|
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: statue of the Virgin Mary | Statement: [Our Lady of the Immaculate Conception Church, Panaji, hasStatuary, statue of the Virgin Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatuary Context triple: [Our Lady of the Immaculate Conception Church, Panaji, hasStatuary, statue of the Virgin Mary]
-
A.
hasStatue
chosen
Indicates that one entity possesses, contains, or is associated with a statue representing or located within it.
-
B.
hasSculpturalFigures
Indicates that something includes or features three-dimensional sculpted figures as part of its form or decoration.
-
C.
statuesBy
Indicates that one entity is the creator, sculptor, or originator of statues depicting or associated with another entity.
-
D.
hasSculptureType
Indicates that an entity is associated with a sculpture and specifies the type or category of that sculpture.
-
E.
topStatue
Indicates that one entity is positioned as a statue on top of 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:37 p.m.