Triple
T7399196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crnogorci |
E170701
|
entity |
| Predicate | citizenshipOverlap |
P13310
|
FINISHED |
| Object | citizens of Montenegro |
—
|
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: citizens of Montenegro | Statement: [Crnogorci, citizenshipOverlap, citizens of Montenegro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citizenshipOverlap Context triple: [Crnogorci, citizenshipOverlap, citizens of Montenegro]
-
A.
citizenshipIssue
Indicates that there is a problem, dispute, or complication concerning an entity’s citizenship status or rights.
-
B.
citizenshipContext
Indicates the legal or social circumstances under which an entity holds or is granted citizenship in a particular state or jurisdiction.
-
C.
definedCitizenship
Indicates that a formal citizenship status has been legally established or specified for an entity.
-
D.
hasDualCitizenship
Indicates that a person is legally recognized as a citizen of two different countries at the same time.
-
E.
citizenshipLinkedTo
chosen
Indicates that there is an established connection between an entity and a specific citizenship status, such as holding, sharing, or being associated with that citizenship.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24dbf288190b8dfea455148841b |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.