Triple
T37552167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormheim |
E933612
|
entity |
| Predicate | capitalOrHub |
P43828
|
FINISHED |
| Object | Valdisdall |
—
|
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: Valdisdall | Statement: [Stormheim, capitalOrHub, Valdisdall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOrHub Context triple: [Stormheim, capitalOrHub, Valdisdall]
-
A.
capitalOrMajorCenter
chosen
Indicates that a location serves as a capital city or a primary major center (political, economic, or cultural hub) for a larger region or entity.
-
B.
capitalLikeCity
Indicates that a capital city shares similar characteristics or status to a particular city.
-
C.
capitalUnder
Indicates that one entity serves as the capital city or administrative center subordinate to, or governed by, another entity.
-
D.
capitalPossiblyAt
Indicates a possible or uncertain capital relationship, where one location may be the capital of another but this is not definitively established.
-
E.
capitalCityHeadquarters
Indicates that the headquarters of an organization or entity is located in the capital city of a specified region or country.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:17 p.m.