Triple
T25769086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labudovo Brdo |
E648967
|
entity |
| Predicate | belongsToSettlement |
P8239
|
FINISHED |
| Object | Belgrade |
—
|
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: Belgrade | Statement: [Labudovo Brdo, belongsToSettlement, Belgrade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToSettlement Context triple: [Labudovo Brdo, belongsToSettlement, Belgrade]
-
A.
belongsToSettlementCategory
Indicates that a settlement is classified under a specific settlement category or type.
-
B.
connectsSettlementRegion
Indicates a relationship where a settlement is linked or associated with a broader geographic region it belongs to or is situated within.
-
C.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
D.
associatedWithSettlement
chosen
Indicates a relationship where an entity is linked or connected to a particular settlement, such as a town, village, or city.
-
E.
hasHumanSettlementDependency
Indicates that one human settlement relies on or is dependent upon another settlement for certain functions, resources, or services.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 22, 2026, 5:13 a.m.