Triple
T34525388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | silver casket of St. Francis Xavier |
E886384
|
entity |
| Predicate | viewableBy |
P173550
|
FINISHED |
| Object | visitors to Basilica of Bom Jesus |
—
|
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: visitors to Basilica of Bom Jesus | Statement: [silver casket of St. Francis Xavier, viewableBy, visitors to Basilica of Bom Jesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewableBy Context triple: [silver casket of St. Francis Xavier, viewableBy, visitors to Basilica of Bom Jesus]
-
A.
viewedBy
Indicates that something has been seen, observed, or watched by a particular entity.
-
B.
isViewableIn
Indicates that one entity can be visually accessed, observed, or displayed within the context, medium, or viewpoint defined by another entity.
-
C.
visibleBy
chosen
Indicates that one entity can be seen or perceived visually by another entity.
-
D.
viewedBySomeAs
Indicates that at least one observer or group perceives or interprets an entity in a particular way or role.
-
E.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
- 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_69f71fb788ec8190a1afec0cfb77dfa5 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.