Triple
T25601435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitanate of Cetinje |
E641796
|
entity |
| Predicate | establishedAsSeatIn |
P164176
|
FINISHED |
| Object | Cetinje |
—
|
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: Cetinje | Statement: [Metropolitanate of Cetinje, establishedAsSeatIn, Cetinje]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsSeatIn Context triple: [Metropolitanate of Cetinje, establishedAsSeatIn, Cetinje]
-
A.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
B.
permanentSeat
Indicates that an entity holds a seat or position that is intended to be ongoing and not subject to regular expiration, rotation, or reappointment.
-
C.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
-
D.
hasPrimarySeat
Indicates that one entity is designated as the main or principal seat, location, or position associated with another entity.
-
E.
claimsSeat
Indicates that an entity takes or asserts possession of a particular seat or seating position.
- F. None of above. chosen
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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 21, 2026, 4:31 p.m.