Triple
T30268720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slavic Pomeranians |
E769725
|
entity |
| Predicate | hadTribalCentersIn |
P17588
|
FINISHED |
| Object | Wolin |
—
|
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: Wolin | Statement: [Slavic Pomeranians, hadTribalCentersIn, Wolin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadTribalCentersIn Context triple: [Slavic Pomeranians, hadTribalCentersIn, Wolin]
-
A.
hasTribalHeadquarters
Indicates that an entity serves as the official tribal headquarters location for a particular tribe or tribal organization.
-
B.
wasStrategicCenterIn
Indicates that an entity functioned as a key strategic center or hub within a specified context, such as a region, period, or conflict.
-
C.
hasMajorHistoricalCentersIn
chosen
Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
-
D.
hasColonialCenter
Indicates that one entity serves as the colonial administrative or control center for another entity.
-
E.
numberOfTribes
Indicates the total count of distinct tribes associated with a given entity or context.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680d27d288190b66d52f002726551 |
completed | May 2, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:43 p.m.