Triple
T36826486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | São Brás |
E910023
|
entity |
| Predicate | equivalentSaint |
P127976
|
FINISHED |
| Object | Saint Blaise |
E264499
|
NE 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: Saint Blaise | Statement: [São Brás, equivalentSaint, Saint Blaise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentSaint Context triple: [São Brás, equivalentSaint, Saint Blaise]
-
A.
equivalentIn
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
-
B.
equivalentInReligion
Indicates that two entities share the same or an essentially identical religious affiliation, tradition, or classification.
-
C.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
D.
equivalentInPantheon
Indicates that two deities from different mythological systems are considered counterparts or functional equivalents within their respective pantheons.
-
E.
équivalentLiturgique
chosen
Indicates that two religious entities are considered liturgically equivalent, serving the same or an interchangeable role within liturgical practice.
- F. None of above.
Provenance (4 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca9c9ef88190b71bcc6f5b4a6182 |
completed | May 3, 2026, 10:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f69f769408190a51551d04c2e0d00 |
completed | June 27, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.