Triple
T851858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monaco |
E18404
|
entity |
| Predicate | sovereigntyRecognizedSince |
P359
|
FINISHED |
| Object | 1861 |
—
|
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: 1861 | Statement: [Monaco, sovereigntyRecognizedSince, 1861]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovereigntyRecognizedSince Context triple: [Monaco, sovereigntyRecognizedSince, 1861]
-
A.
independenceRecognized
chosen
Indicates that one entity formally acknowledges another entity’s status as independent and self-governing.
-
B.
establishedOnIndependenceFrom
Indicates that an entity (such as a state or organization) was founded or formally established on the date it gained independence from another governing authority.
-
C.
dateOfUNMembership
Indicates the specific date on which an entity officially became a member of the United Nations.
-
D.
lastTrustTerritoryIndependenceYear
Indicates the year in which the last remaining trust territory associated with an entity achieved independence.
-
E.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac22de288190913714d41e5a8e12 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa81ef348190b067f817574e9efe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.