Triple
T35118973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Many-Faced God |
E1014115
|
entity |
| Predicate | worshipCenterRegion |
P148439
|
FINISHED |
| Object | Free City of Braavos |
—
|
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: Free City of Braavos | Statement: [Many-Faced God, worshipCenterRegion, Free City of Braavos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipCenterRegion Context triple: [Many-Faced God, worshipCenterRegion, Free City of Braavos]
-
A.
majorRegionOfWorship
Indicates the primary geographic region where a deity, religion, or cult is predominantly worshipped.
-
B.
devotionalRegion
chosen
Indicates the geographic area or region in which a particular devotional practice, cult, or form of worship is observed or centered.
-
C.
worshipCenter
Indicates that one entity serves as a place or facility where another entity engages in religious worship or related spiritual activities.
-
D.
liturgicalUseRegion
Indicates the geographic region or area in which a particular liturgical practice, text, or usage is observed or applied.
-
E.
missionaryRegion
Indicates that an entity carries out or is associated with missionary activities within a specified geographic region.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.