Triple
T7286900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandžak |
E163891
|
entity |
| Predicate | wasAdministrativeUnitType |
P52949
|
FINISHED |
| Object | sanjak |
—
|
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: sanjak | Statement: [Sandžak, wasAdministrativeUnitType, sanjak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAdministrativeUnitType Context triple: [Sandžak, wasAdministrativeUnitType, sanjak]
-
A.
administrativeUnitType
chosen
Indicates the specific kind or category of administrative unit involved in the relationship (e.g., city, county, province).
-
B.
isAdministrativeUnit
Indicates that one entity functions as an official administrative division or unit within the governance or organizational structure of another entity.
-
C.
hasAdministrativeUnit
Indicates that one entity possesses, contains, or is associated with another entity that functions as its administrative subdivision or governing unit.
-
D.
representsAdministrativeUnit
Indicates that one entity serves as or corresponds to the administrative unit governing or organizing another entity.
-
E.
laterAdministrativeUnit
Indicates that one administrative unit succeeds or replaces another in time, coming into effect at a later date.
- 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb532adc8190bcbbf31bb54383fb |
completed | March 27, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.