Triple
T19255565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltal |
E481507
|
entity |
| Predicate | temporarySettlementType |
P135066
|
FINISHED |
| Object | seasonal camp |
—
|
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: seasonal camp | Statement: [Baltal, temporarySettlementType, seasonal camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarySettlementType Context triple: [Baltal, temporarySettlementType, seasonal camp]
-
A.
consideredTemporarySettlementOf
Indicates that one location is regarded as a provisional or non-permanent settlement associated with another place.
-
B.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
C.
currentSettlementType
Indicates the specific category or classification of settlement (such as village, town, or city) that currently applies to an entity.
-
D.
typeOfSettlement
Indicates the specific category or classification of a settlement (e.g., city, town, village) that characterizes what kind of settlement it is.
-
E.
settlementMode
Indicates the method or process by which a financial or transactional obligation is settled or completed between parties.
- F. None of above. chosen
Provenance (4 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb3572c08190a55f1c71cdb18b42 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:28 p.m.