Triple
T30783385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA |
E783885
|
entity |
| Predicate | administrativeSeatForCodeArea |
P191200
|
FINISHED |
| Object | Sępopol |
—
|
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: Sępopol | Statement: [NBA, administrativeSeatForCodeArea, Sępopol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeSeatForCodeArea Context triple: [NBA, administrativeSeatForCodeArea, Sępopol]
-
A.
administrativeCouncilArea
Indicates that one entity is an administrative council area within which the other entity is located or governed.
-
B.
adminDistrictSeat
Indicates that one entity serves as the administrative center or capital seat of an administrative district to which the other entity belongs.
-
C.
seatOfLocalGovernment
chosen
Indicates that one entity serves as the administrative center or headquarters where the local government of another entity is based and operates.
-
D.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
E.
denotesAdministrativeArea
Indicates that one entity designates or specifies another entity as its relevant administrative area or jurisdiction.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 29, 2026, 8:41 p.m.