Triple
T35038300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syro-Malabar eparchies |
E1010989
|
entity |
| Predicate | areErectedBy |
P25865
|
FINISHED |
| Object | Holy See |
—
|
NE NERFINISHED |
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: Holy See | Statement: [Syro-Malabar eparchies, areErectedBy, Holy See]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areErectedBy Context triple: [Syro-Malabar eparchies, areErectedBy, Holy See]
-
A.
erected
Indicates that one entity caused a structure or object to be built or put upright, typically in a deliberate and often permanent manner.
-
B.
erectedBy
chosen
Indicates that something (such as a structure, monument, or installation) was constructed, set up, or raised by a particular agent or entity.
-
C.
isBuildingOf
Indicates that one entity is a building that belongs to, houses, or is associated with another entity (such as an organization, institution, or complex).
-
D.
builtUpBy
Indicates that something has been constructed, developed, or formed through the actions or contributions of a specified agent or process.
-
E.
eraOfManyBuildings
Indicates a time period during which many buildings were constructed or existed.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858f4eac8190a71bc6fddd380cda |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.