Triple
T10229700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronoberg County |
E243306
|
entity |
| Predicate | coversPartsOf |
P52847
|
FINISHED |
| Object | historical province of Småland |
—
|
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: historical province of Småland | Statement: [Kronoberg County, coversPartsOf, historical province of Småland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversPartsOf Context triple: [Kronoberg County, coversPartsOf, historical province of Småland]
-
A.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
B.
consideredPartOf
chosen
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
-
C.
isOnlyPartOf
Indicates that an entity is a component exclusively of a specific whole and not of any other whole.
-
D.
servesPartOf
Indicates that one entity functions as a service or provider that operates within, or as a component of, another larger system or context.
-
E.
containsPortionOf
Indicates that one entity includes or holds a part, segment, or fraction of another entity.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:19 a.m.