Triple
T35044901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konispol Municipality |
E1011169
|
entity |
| Predicate | partOfStateTerritory |
P65771
|
FINISHED |
| Object | Republic of Albania |
—
|
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: Republic of Albania | Statement: [Konispol Municipality, partOfStateTerritory, Republic of Albania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfStateTerritory Context triple: [Konispol Municipality, partOfStateTerritory, Republic of Albania]
-
A.
partOfTerritory
chosen
Indicates that one geographic or administrative area is contained within, and forms a constituent portion of, another territory.
-
B.
stateOfTerritory
Indicates the political or administrative state that has authority over a given territory.
-
C.
federalTerritory
Indicates that one entity is designated as a federal territory under the jurisdiction or authority of another (typically a federal government or state).
-
D.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
-
E.
missionTerritoryOf
Indicates that a specified territory is under the jurisdiction or scope of a particular mission.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0075be7f54819081ab12bc1dab53bb |
completed | May 10, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a0073a19030819098c23faa3adcb96e |
completed | May 10, 2026, 12:01 p.m. |
Created at: May 3, 2026, 4:01 p.m.