Triple
T31840031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bessarabian Metropolitanate |
E812778
|
entity |
| Predicate | claimsCanonicalTerritory |
P647
|
FINISHED |
| Object | Moldova |
—
|
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: Moldova | Statement: [Bessarabian Metropolitanate, claimsCanonicalTerritory, Moldova]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsCanonicalTerritory Context triple: [Bessarabian Metropolitanate, claimsCanonicalTerritory, Moldova]
-
A.
claimsTerritory
chosen
Indicates that one entity asserts ownership, control, or sovereign rights over a specific geographic area or region.
-
B.
hasCanonicalTerritory
Indicates that an entity possesses an officially recognized or standard territorial area associated with it.
-
C.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
D.
recognizedTerritory
Indicates that one entity formally acknowledges another entity’s claim of authority or ownership over a specific geographic area.
-
E.
usesTerritoryFor
Indicates that an entity employs or exploits a particular territory for a specific purpose, function, or activity.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 30, 2026, 11:49 p.m.