Triple
T16665850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Service Troops |
E404978
|
entity |
| Predicate | raisedFrom |
P18556
|
FINISHED |
| Object | Idar State |
E772541
|
NE 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: Idar State | Statement: [Imperial Service Troops, raisedFrom, Idar State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Idar State Context triple: [Imperial Service Troops, raisedFrom, Idar State]
-
A.
Idar State
chosen
Idar State was a princely state in western India during the British Raj, located in present-day Gujarat.
-
B.
Svarstad
Svarstad is a Norwegian surname associated with individuals such as Maren Svarstad.
-
C.
Heidal
Heidal is a village in Innlandet county, Norway, known for its traditional wooden architecture and scenic location in the Gudbrandsdalen valley.
-
D.
Verdal
Verdal is a municipality in central Norway known for its agricultural landscape, industrial activity, and the historic battlefield of Stiklestad.
-
E.
Jørpeland
Jørpeland is a town in Rogaland county, Norway, known as a local industrial and service hub and a gateway to the nearby Lysefjord and Preikestolen (Pulpit Rock).
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9cd7ec819084aa9b2830874bf5 |
completed | April 18, 2026, 12:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0084d21ed4819089fc70f92653694d |
completed | May 10, 2026, 1:14 p.m. |
Created at: April 10, 2026, 5:18 a.m.